Today we are making available a patch release to the ASP.NET Core 1.0 release.  This patch contains some updates to MVC, Routing, AntiForgery, Entity Framework Core, and the Kestrel server.  Release notes and links to the issues that are addressed for these packages are available on GitHub.  There are updated ASP.NET Core templates available as part of the “Microsoft .NET Core 1.0.1 – VS 2015 Tooling Preview 2” release in the Tools section on the .NET Downloads page.

There are also several updates to the .NET Core framework, SDK, and Windows Server Hosting components that you will need to install in order to use this version of the ASP.NET Core framework.  We recommend installing this update on your development and production machines to also address a security advisory that was issued. More details about that advisory can be found on TechNet

Support

This is a long-term- support release that we are issuing, and paid support is available as part of the 1.0.x release train for three years starting with the 1.0.0 release in late June 2016.  For more information about the .NET Core / ASP.NET Core release and support cycle, check our support page for more details.

Updating My Existing Application

To update an application that you are currently working on, you simply need to update the package references to the latest 1.0.1 versions of the packages in your project.json file..

Note: the IISIntegration package is shown for comparison purposes only.  It was not updated in this release.

You can “lock in” to a specific version of a package by referencing the full version number of the package, as shown in the IISIntegration and Kestrel packages on lines 1 and 2.  We recommend you update the following packages version number to 1.0.1 if you have them referenced in your project.json:

• Microsoft.EntityFrameworkCore
• Microsoft.AspNetCore.Server.Kestrel
• Microsoft.AspNetCore.Mvc
• Microsoft.AspNetCore.Antiforgery
• Microsoft.AspNetCore.Routing

The last two packages, Antiforgery and Routing, are referenced by the MVC package.  If you are not directly referencing them in your project, you do not need to do any extra work to update them.  The package manager will automatically include the updated versions when it updates the MVC package.

Summary

Most of the bugs we are addressing were identified by customers and don’t have easy workarounds.  Thank you to the participants on our GitHub issues lists and those who are submitting pull-requests.  We look forward to working with you on the next release of ASP.NET Core.