Releases: dotnet/aspnetcore
v2.2.1
v2.1.7
v3.0.0-preview-18579-0056
v2.2.0
ASP.NET Core release notes
We have disabled view recompilation when .cshtml change by default (except for the Development environment). A new flag called AllowRecompilingViewsOnFileChange has been introduced in RazorViewEngineOptions, which can be used to configure whether the view engine will watch for file changes. The settings is set to false by default for all environments but Development. If you are using Visual Studio to debug, then it will launch the application in the Development environment by default. You can find more details about the change by looking at this PR: https://github.com/aspnet/Mvc/pull/8369/files
In case you would like to keep the view recompilation enabled for your project, you can choose so by configure Razor options in Startup.ConfigureService method using the following code block:
services.AddMvc()
.SetCompatibilityVersion(CompatibilityVersion.Version_2_2)
.AddRazorOptions(options => options.AllowRecompilingViewsOnFileChange = true);
Repos
2.1.6
The list of changes in this release is available here:
2.2.0-preview3
Known issues: aspnet/Announcements#323
2.1.5
Read more about the 2.1.5 update here: https://blogs.msdn.microsoft.com/dotnet/2018/10/02/net-core-october-2018-update/
2.2.0-preview2
ASP.NET Core 2.2.0-preview2
For more details, see the blog post here: https://blogs.msdn.microsoft.com/webdev/2018/09/12/asp-net-core-2-2-0-preview2-now-available.
To see all issues closed in the 2.2.0 Preview 2 milestone, see the results of this query.
2.2.0-preview1
ASP.NET Core 2.2.0 Preview 1 Release Notes
We are pleased to announce the release of ASP.NET Core 2.2.0 Preview 1.
See also the release notes for .NET Core 2.2 Preview 1.
Known Issues
- Broken links in the ASP.NET Core Web Application (Razor Pages) template
The Page1, Page2, and Privacy links on the home page of the ASP.NET Core Web Application (Razor Pages) template incorrectly point to controllers and actions that don't exist. To work around this issue update the links fixup links to point to the corresponding Razor Pages (Note: the Page1 and Page2 links in the navbar don't have corresponding pages and this is by design as they are only intended to illustrate how to add links to the navbar using Bootstrap). - Styling issues with the login partial when enabling Individual User Accounts authentication
The Register, Login, and User Profile links in the login partial are misaligned. Update the login partial to correct the styling issue. - Default identity UI only supports Bootstrap 4
The default identity UI was updated in this release to use Bootstrap 4. Apps that require Bootstrap 3 will need to override the default identity UI using the scaffolder and update the generated pages to switch back to Bootstrap 3. An option to use Bootstrap 3 instead of Bootstrap 4 with the default identity UI will be added in a future preview release. - Scaffolding generates Bootstrap 3 content into Boostrap 4 based projects
The MVC, Razor Pages and Identity scaffolders generate have not been updated to Bootstrap 4 and still generate Bootstrap 3 based content. This will be addressed in a future preview release. To workaround the limitation manually update the styles to Bootstrap 4. - Publishing to Azure App Service results in error saying that ANCM v2 is not installed
To deploy an ASP.NET Core 2.2 app to Azure App Service follow these instructions to install the required site extension.
2.1.4
ASP.NET Core 2.1.4
For more details, see the blog post here: https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-core-september-2018-update.