rune on 12 Apr, 2017 05:08 PM
It's not supported yet, but almost complete and will be rolled out over the next couple of weeks -- so we should have full support ready by the end of this month! I'll make sure to follow up here as soon as it's ready.
rune on 11 May, 2017 09:04 PM
Unfortunately it's not enabled on the build servers just yet (although both the build servers and app servers now have the latest .NET Core SDKs and runtimes installed). We're working hard to get the build server integration implemented properly, and hope to release this early next week.
About how far are you away from supporting .NET Core builds? I see that you mentioned that you were possibly going to have this enabled earlier this week... Did this happen, or are there still kinks to work out?
rune on 30 May, 2017 03:08 AM
Apologies for the slow response and thanks for your patience! Quite a few blockers have held this release back for way too long, but fortunately those are addressed now and the build infrastructure is finally being updated this week to support .NET Core builds.
You may want to wait a couple of days for a couple of minor publishing features to be deployed (along with more documentation), but in case you want to .NET Core now you can do so with a couple of tweaks; currently you'd just need to trigger the Publish target and set the PublishDir property yourself in the new VS2017/MsBuild 15 project formats. That's pretty straightforward as you can see in the example csproj file below, which uses a default ASP.NET Core (Core FX) template app created with VS017:
The same configuration is required for ASP.NET Core apps that use the regular .NET Framework, which also works today! Everything else should work as usual, including NuGet restore (which also supports the new package configuration and formats) and the regular solution file conventions for the build process.
I'll make sure to give you a heads up here when the publish operation has been integrated, but in the meantime please don't hesitate to reach out with any feedback or questions!
I'm not going to lie, I'm a little bit disappointed about this topic. It's not the "slowness". Everyone knows this task can be huge, there's a lot of possible complications, dependencies etc. Just the communication is a little on the short side.
Maybe if we could just get really short snippet-sized updates if there's some problem, if it's still on the way?
rune on 23 Jun, 2017 08:03 AM
I agree that the communication has fallen short on this topic, and the project has been plagued by delays -- will post more frequent updates going forward so you can plan accordingly.
The good news is that most of the missing pieces are now finally being deployed to the platform. Earlier today worker servers in the US region were updated to support ASP.NET Core (.NET Core and regular .NET framework) environment configuration, with configuration variables injected as environment variables. This can be useful for setting for setting the ASPNETCORE_ENVIRONMENT and other configuration you want to override. It also works "out of the box" with the Visual Studio ASP.NET Core templates as these will use environment variable configuration by default, but please don't hesitate to reach out with any questions or feedback.
Servers in the EU region and private regions are scheduled to be updated tomorrow. Full build server support will also be over the weekend, and I'll keep you updated here as this progress. For the time being you can still just set the publish target and directory as described earlier to make sure the website is compatible with AppHarbor's current artifact directory structure.
So Rune and I must have been composing our posts at the same time. I can verify that the AH updates that Rune talked about are working and the configuration values are being injected into the environment.
So no need for the web.config ConfigurationSource/ConfigurationProvider above. Just really, really bad timing - I swear when I started the above code tonight, the environment didn't have the config values.