Updates for .NET Core, ASP.NET Core runtime and .NET Core SDK versions RRS feed

  • General discussion

  • We keep the Azure App Service platform up to date with latest ASP.NET Core and .NET Core runtime as well as latest .NET Core SDK versions. It is recommended to leverage the latest versions for ASP.NET Core components for up to date runtime and tooling improvements. Considering this recommendation, the relevance for older versions is low and we plan to make the following changes starting March 2017:

    Deprecate older, unsupported, pre-releases: 1.0.0-rc2

    Applications running on these older pre-releases are no longer supported and must update to a supported version of the framework. For details of the supported versions of .NET see the .NET Core support documentation.

    Remove redundant runtimes: 1.0.0, 1.0.1, 1.0.3

    Applications targeting older patch releases will automatically run on 1.0.4 instead of 1.0.0, 1.0.1, or 1.0.3. Because these runtimes are not going to be used by .NET Core applications we will remove them. No existing applications should be impacted by this removal.

    Deprecate older, unsupported, SDK versions: 1.0.0-preview1-002702, 1.0.0-preview2-003121, 1.0.0-preview2-003131, 1.0.0-preview2.1-003155, 1.0.0-preview3-004056, 1.0.0-preview4-004233.

    Old versions of pre-release SDKs are no longer supported and applications being built with this tooling must be updated to csproj and the latest SDK. We are leaving two project.json based SDKs installed to make this migration easier, but in the future they will be removed as well. If your project requires a project.json file please specify one of the following SDK versions available in App Service in the global.json file to avoid auto-selection of the latest SDK version: 1.0.0-preview2-003156, 1.0.0-preview2-1-003177.

    What does this mean for my applications?

    If you are using the SDK on Azure App Service (e.g. using Kudu to build your application), then you need to:

    1. If you are using project.json, you should migrate your project to csproj with the latest stable release of the tooling.
    2. If you are using csproj with one of the removed versions of the SDK then you should check that your application works with the stable 1.0.0 SDK version before re-deploying.

    If you are not using the SDK but have a running application on Azure App Service then:

    1. If you are using the 1.0.0-rc2 runtime, your application is going to break when it is removed. You must upgrade to a stable version of the runtime, 1.0.4 being the closest supported patch release to 1.0.0-rc2.
    2. If you are using 1.0.0, 1.0.1, or 1.0.3, then you don’t need to do anything.

    Daria Grigoriu

    Tuesday, March 7, 2017 7:00 PM

All replies

  • I don't think this is true. 1.1.2 and 1.1.3 are not on my Azure App Service instance. 
    Thursday, May 11, 2017 4:07 PM