-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Azure App Service fails to load .net Core application after upgrade to 2.1.4 #3531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @ld0614 , what does your app's CSPROJ look like? I think in general you don't need to reference 2.1.4 explicitly. You would only reference that if you have a specific need for 2.1.4, such as requiring a bug fix. I'm guessing Azure App Services doesn't have 2.1.4 yet (but I think it will soon). In general we recommend that apps require 2.1, but not specific patch versions, so it will run on any 2.1.x instance. |
Yes, should be done by tomorrow. But regardless, targeting 2.1 without a specific patch version is the way to go. |
Thanks for the info, the relevant parts of the csproj are:
I haven't manually been modifying this file, just upgrading the packages through NuGet in Visual Studio as they become available, after an upgrade, should I be remodifying the package reference back to 2.1? |
Set it to |
I wish VS would display information about the "roll-forward" feature. |
Relevant #3292 |
FWIW, the 2.1.4 release to App Service is now complete. |
Thanks for the update @davidebbo. I'll close the issue as that (and the implicit versioning) has solved my issue. My suggestion to avoid similar things happening to people like me would be to update the description text of the NuGet package just to mention that the runtime must match or exceed the nuget version: Thanks |
After upgrading the .net Core nuget packages last night from 2.1.3 to 2.1.4 to mitigate the published security issues, I attempted to push these to an Azure App Service.
However I get the following error:

dotnet --info of Azure App Service
dotnet --info of development machine (where it works)
The packaged deployed is using the standard Azure DevOps (VSTS) Build and publish tasks. My guess is that Azure App Service requires the latest patches to support the updated nuget packages, is this correct?
Is it possible to use a dedicated version of .net core on an Azure app service by using portable binary compliation?
Is there a clear guide on application lifecycles in respect to .net core packages and versions? I've had a look but wasn't able to find anything describing when nuget packages should be updated vs the runtime they run on etc.
The text was updated successfully, but these errors were encountered: