NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #529 most downloaded on NuGet
ASP.NET Core middleware for filtering out requests with unknown HTTP host headers.
Latest stable
2.3.14
Last release 12 days ago
10 Nov 2026
Ships unpredictably
gaps range from 3 weeks to 6.1 years
Some releases are documented
notes for 3 of 11 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
16 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
We have disabled view recompilation when .cshtml change by default (except for the Development environment). A new flag called AllowRecompilingViewsOn
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:
<pre> services.AddMvc() .SetCompatibilityVersion(CompatibilityVersion.Version_2_2) <b>.AddRazorOptions(options => options.AllowRecompilingViewsOnFileChange = true);</b> </pre>
Nothing published for this version
Nothing published for this version
Nothing published for this version
We are pleased to announce the release of ASP.NET Core 2.1.1.
We are pleased to announce the release of ASP.NET Core 2.1.1.
We are pleased to announce the release of ASP.NET Core 2.1.0.
We are pleased to announce the release of ASP.NET Core 2.1.0.
Warning when building new ASP.NET Core project that targets .NET Framework Building a new ASP.NET Core project that targets net461 produces the following warning:
There was a mismatch between the processor architecture of the project being built "x86" and the processor architecture of the reference "c:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.mvc.razor.viewcompilation\2.1.0-rtm-30796\build\netstandard2.0\Microsoft.AspNetCore.Mvc.Razor.ViewCompilation-x64.exe", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project
Workaround: Remove the reference to the Microsoft.AspNetCore.Mvc.Razor.ViewCompilation package.
Windows authentication is not enabled after creating project with the Windows authentication option selected When creating a template with Windows authentication, the settings to enable Windows authentication in launchSettings.json are not applied. Workaround: Modify launchSettings.json as follows:
"windowsAuthentication": true,
"anonymousAuthentication": false,
NullReferenceException when using a custom IAuthorizationPolicyProvider and AllowCombiningAuthorizeFilters is set to true
Using a custom IAuthorizationPolicyProvider and setting AllowCombiningAuthorizeFilters to true causes a NullReferenceException.
Workaround: Disable AllowCombiningAuthorizeFilters or use a single AuthorizeFilter
XmlSerializerOutputFormatter throws InvalidCastException for async action methods
Invoking an Async action method may result in an InvalidCastException when using the XmlSerializerOutputFormatter.
Workaround: Wrap the return type in ActionResult<T>. Ex. replace the return type Task<IEnumerable<string>> with Task<ActionResult<IEnumerable<String>>>.
Nothing published for this version
Nothing published for this version
One column per quarter.