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.

• New features
• Bug fixes

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.

2.1.3

ASP.NET Core 2.1.3

We are pleased to announce the release of ASP.NET Core 2.1.3.

Bugs Fixed

• Update StackExchange.Redis.StrongName (aspnet/Caching#396)
• Migrations: multiple references to the same owned type carries into subsequent migrations (dotnet/efcore#12107)
• Invalid column name: orderby uses a column alias that does not exist (dotnet/efcore#12180)
• 2.1.0 can't do Value Conversions on complex IEnumerable types like JObject (newtonsoft) (dotnet/efcore#12203)
• In-Memory concurrency check is not doing a sequence check when using a byte array type (dotnet/efcore#12214)
• InvalidOperationException while adding or retrieving object graph (dotnet/efcore#12227)
• Projection query throws InvalidCastException trying to convert Int32 to Boolean (dotnet/efcore#12280)
• Value Conversion of custom struct type throws exception if it doesn't implement == and != operators (dotnet/efcore#12290)
• SumAsync throw Exception when used over float? (dotnet/efcore#12314)
• Incorrect SQL generated for Count over Group By (dotnet/efcore#12351)
• Null checking in anonymous projection throws InvalidOperationException (dotnet/efcore#12412)
• InvalidCastException when casting to/from enum in query (dotnet/efcore#12557)
• The ASP.NET Core runtime installer does not delete files on uninstall (#3286)
• ActivePage declarations missing on scaffolded Identity UI (aspnet/Identity#1866)
• Consistently handle connection aborts (aspnet/KestrelHttpServer#2636)
• MemoryPoolBlock.Dispose can throw and ODE during server shutdown leading to an error log from the Socket Transport (aspnet/KestrelHttpServer#2638)
• ProducesResponseType doesn't infer the type from ActionResult<T> (aspnet/Mvc#7875)
• Conventional routing with custom templates not working when you have area attributes (aspnet/Mvc#7959)
• Validation occurs against declared type rather than real type (aspnet/Mvc#7968)
• Razor runtime compilation produces errors if running on a shared runtime that's rolled forward (aspnet/Mvc#7969)
• BindingSource for IEnumerable<IFormFile> ApiController parameters on is incorrectly inferred as FromBody (aspnet/Mvc#7970)
• Copy-pasting an item in a Razor Class Library project adds junk to the project file (aspnet/Razor#2384)
• Having whitespace in username makes Razor builds slower (aspnet/Razor#2406)
• Razor compilation gives error CS2017: Cannot specify /main if building a module or library (aspnet/Razor#2407)
• Role/claim changes in identity aren't persisted into the auth cookie (aspnet/Security#1788)
• SaveTokens + GetTokenAsync does not work for JwtBearer (aspnet/Security#1809)
• Update AddSignalRCore to respect user registered services (aspnet/SignalR#2561)
• ResponseCache attribute on RazorPages Error handler method should be moved to model (aspnet/Templating#565)
• Hosting Bundle installer removes RC version of 2.1.0, breaking all RC apps (dotnet/core#1655)

Known issues

Razor compilation is slow if you have a space in your username

aspnet/Razor#2406 - when building an ASP.NET Core app as a user with a space in username, build times may be a few minutes more than it takes when building as a different user.

Solutions:

1. Add a PackageReference to your project file (.csproj) to update the Razor compiler.

<PackageReference Include="Microsoft.AspNetCore.Razor.Design" Version="2.1.2" />

2. Change your username to something without spaces.

EntityFrameworkCore commands in the Visual Studio Package Manager Console issue a warning

When using EntityFrameworkCore commands in the Package Manager Console, you may see a warning with this text.

The EF Core tools version '2.1.1-rtm-30846' is older than that of the runtime '2.1.2-rtm-30921.' Update the tools for the latest features and bug fixes.

Available solutions:

1. Do nothing. This warning can be ignored for now. We are working on a fix for a future 2.1 update.
2. Update the version of the Microsoft.AspNetCore.App package.

<PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.3" />

⚠️ This may have unintended consequences on your deployment environment. If the deployment environment does not have the the 2.1.3 runtime, apps will fail to start with an error. In Azure or apps hosted behind IIS, this may appear as HTTP 502.5 error.

It was not possible to find any compatible framework version
The specified framework 'Microsoft.AspNetCore.App', version '2.1.3' was not found.

Version mismatches can cause apps to fail with System.IO.FileLoadException

Some ASP.NET Core 2.1 applications will be affected by a bug in the .NET Core host (see dotnet/core-setup#4512) which can cause apps to fail with System.IO.FileLoadException. The issue may also be present in your app, even if the app does not fail with System.IO.FileLoadException.

This issue and workarounds are described in greater detail in #3503

2.1.2

ASP.NET Core 2.1.2 Release Notes

This update includes two security fixes. Please see the following links for details.

• aspnet/Announcements#310
• aspnet/Announcements#311

2.1.1

ASP.NET Core 2.1.1 Release Notes

We are pleased to announce the release of ASP.NET Core 2.1.1.

• Bug fixes

2.1.0

ASP.NET Core 2.1.0 Release Notes

We are pleased to announce the release of ASP.NET Core 2.1.0.

• New features
• Bug fixes

Known Issues

• 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>>>.

2.1.0-rc1

ASP.NET Core 2.1.0-rc1 Release Notes

We are pleased to announce the release of ASP.NET Core 2.1.0-rc1.

• New features
• Bug fixes

Known Issues

• ASP.NET Core applications that use SQLite and Libuv may not work correctly when deployed against the new linux-musl-x64 RuntimeIdentitifer
  Users may encounter a __memcpy_chk: symbol not found or __cmsg_nxthdr: symbol not found error at runtime. See aspnet/libuv-package#23 for additional details.
  Workaround: For apps using SQLite, upgrade to SQLitePCLRaw 1.1.11 by adding <PackageReference Include="SQLitePCLRaw.bundle_green" Version="1.1.11" /> to your project file. For apps using Libuv, exclude Libuv from the dependency graph by adding <PackageReference Include="Libuv" Version="1.10.0" ExcludeAssets="Native" /> to your project file.
• SignalR: System.ArgumentException: The output byte buffer is too small to contain the encoded data
  when sending non-ascii characters using the JSON protocol
  This is a known issue that will be addressed before 2.1.0 is released