Skip to content

2.1.3
Compare
Choose a tag to compare
@natemcmaster natemcmaster released this 21 Aug 18:33
2.1.3
7119fc7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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" />
  1. 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

Assets 2
Loading