Pre-release
Pre-release

@ryanbrandenburg ryanbrandenburg released this Sep 12, 2018

Assets 2

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.

Pre-release
Pre-release

@natemcmaster natemcmaster released this Aug 22, 2018

Assets 2

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.

@ryanbrandenburg ryanbrandenburg released this Sep 11, 2018

Assets 2

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.

@natemcmaster natemcmaster released this Aug 21, 2018

Assets 2

ASP.NET Core 2.1.3

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

Bugs Fixed

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

@danroth27 danroth27 released this Jul 10, 2018 · 7 commits to master since this release

Assets 2

ASP.NET Core 2.1.2 Release Notes

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

@danroth27 danroth27 released this Jul 10, 2018 · 7 commits to master since this release

Assets 2

ASP.NET Core 2.1.1 Release Notes

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

@danroth27 danroth27 released this May 30, 2018

Assets 2

ASP.NET Core 2.1.0 Release Notes

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

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

Pre-release
Pre-release

@danroth27 danroth27 released this May 7, 2018

Assets 2

ASP.NET Core 2.1.0-rc1 Release Notes

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

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
Pre-release
Pre-release

@danroth27 danroth27 released this Apr 12, 2018

Assets 2

ASP.NET Core 2.1.0-preview2 Release Notes

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

Breaking Changes

  • For a list of the breaking changes for this release please refer to the issues in the Announcements repo.

Known Issues

  • HTTPS still enabled for IIS Express even when specifying the --no-https option on the command-line or in VS Workaround: disable HTTPS for IIS Express after the project template is created.
  • Azure Application Insights light-up fails Workaround: explicitly reference the Azure Application Insights packages in your app.
  • Using the MVC test fixture results in 404 responses for valid requests This is a known issue in this release that will get addressed in a future preview.
  • Code generated by the Identity scaffolder fails to compile Workaround: update the generated _ViewStart.cshtml to correct the typo in the layout path.

@danroth27 danroth27 released this Nov 15, 2017

Assets 2

ASP.NET Core 2.0.3 Release Notes

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

You can find details on the issues fixed in this release for the following components on their corresponding release pages:

Breaking Changes

There are no breaking changes in this release.

Known Issues

There are no known issues with this release.