Skip to content

Releases: dotnet/aspnetcore

RC1

18 Nov 15:31
@danroth27 danroth27
v1.0.0-rc1-final
5569257
Compare
Choose a tag to compare
RC1 Pre-release
Pre-release

ASP.NET 5 RC1 Release Notes

We are pleased to announce the release of ASP.NET 5 RC1!

Please refer to our documentation for instructions on installing ASP.NET 5 beta8 for Windows, Mac, and Linux

You can find details on the new features and bug fixes in rc1 for the following components on their corresponding release pages:

To find out what's new in .NET Core in this release please refer to the .NET Core RC release notes.

Breaking Changes

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

Known Issues

  • Tooling known issues Please see the Known Issues list in the Tooling repo
  • No .NET Core on CentOS This release does not support running on .NET Core on CentOS or derivatives. The issues with running on CentOS will be addressed in a future release.
  • Unable to build for full .NET Framework using the .NET Core based DNX on OS X and Linux You cannot build DNX projects that target the full .NET Framework (ex dnx451, dnx46) using the .NET Core based DNX on OS X and Linux. To work around this issue remove the corresponding targets from the frameworks section in project.json.
  • Applications hosted behind IIS uses in memory keys for data protection When hosted a website behind IIS the Data Protection stack does not find a suitable place to store the keyring, and uses in memory keys. This means that when your application restarts all forms authentication tokens will be invalid and users will have to login again. In addition any data you protected will no longer be able to be unprotected. Please see aspnet/Announcements#110 for options for dealing with this issue.
  • On OS X and Linux keys are stored unencrypted under the user profile path You should ensure permissions for the ~/.aspnet/DataProtection-Keys directory are limited to the user account your application runs as. See aspnet/Announcements#111 for more details.
Assets 2

beta8

15 Oct 17:29
@danroth27 danroth27
v1.0.0-beta8
86c7501
Compare
Choose a tag to compare
beta8 Pre-release
Pre-release

ASP.NET 5 Beta8 Release Notes

We are pleased to announce the release of ASP.NET 5 beta8!

Please refer to our documentation for instructions on installing ASP.NET 5 beta8 for Windows, Mac, and Linux

Documentation and samples for ASP.NET 5 can be found at http://docs.asp.net.
You can find details on the new features and bug fixes in beta8 for the following components on their corresponding release pages:

Breaking Changes

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

Known Issues

  • Tooling known issues Please see the Known Issues list in the Tooling repo
  • No .NET Core on CentOS This release does not support running on .NET Core on CentOS or derivatives. The issues with running on CentOS will be addressed in a future release.
  • Unable to build for full .NET Framework using the .NET Core based DNX on OS X and Linux You cannot build DNX projects that target the full .NET Framework (ex dnx451, dnx46) using the .NET Core based DNX on OS X and Linux. To work around this issue remove the corresponding targets from the frameworks section in project.json.
Assets 2

beta7

02 Sep 22:23
@danroth27 danroth27
v1.0.0-beta7
4f92744
Compare
Choose a tag to compare
beta7 Pre-release
Pre-release

ASP.NET 5 Beta7 Release Notes

We are pleased to announce the release of ASP.NET 5 beta7! ASP.NET 5 beta7 ships publicly as NuGet packages on https://nuget.org and includes a tooling update for Visual Studio 2015 RTM.

To use ASP.NET 5 beta7 with Visual Studio 2015, you will need to download and install the beta7 version (14.0.60831.0) of ASP.NET and Web Tools 2015.

You can also try out ASP.NET 5 with Visual Studio Code on Windows, Mac and Linux!

You can find documentation and samples for ASP.NET 5 at http://docs.asp.net.

You can find details on the new features and bug fixes in beta7 for the following components on their corresponding release pages:

Breaking Changes

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

Known Issues

  • Tooling known issues Please see the Known Issues list in the Tooling repo
  • Limitations of .NET Core on OS X and Linux Support for .NET Core on OS X and Linux is still in early preview. Known limitations include:
    • Cryptography: Some of the System.Security.Cryptography.X509Certificates library is not yet implemented.
    • Networking: Most of the networking libraries are not yet available. System.Net.Primitives and System.Net.NameResolution are only partially functional and System.Net.Http works only for common success scenarios.
    • I/O: Paths up to the system-supported max path length are allowed, except for a few situations related to loading applications, assemblies, and resources.
    • Globalization: Culture is assumed to be invariant and string operations related to sorting and searching assume ASCII.
    • Data: SqlClient is not currently functional.
  • Unable to build for full .NET Framework using the .NET Core based DNX on OS X and Linux You cannot build DNX projects that target the full .NET Framework (ex dnx451, dnx46) using the .NET Core based DNX on OS X and Linux. To work around this issue remove the corresponding targets from the frameworks section in project.json.
  • "Unable to load DLL 'api-ms-win-core-libraryloader-l1-1-0'" error when using the EF7 provider for SQLite on .NET Core on OS X and Linux This is a known issue that will be addressed in a future release.
Assets 2

beta6

28 Jul 19:58
@danroth27 danroth27
v1.0.0-beta6
bf6b720
Compare
Choose a tag to compare
beta6 Pre-release
Pre-release

ASP.NET 5 Beta6 Release Notes

We are please to announce the release of ASP.NET 5 beta6! ASP.NET 5 beta6 ships publicly as NuGet packages on https://nuget.org and includes a tooling update for Visual Studio 2015 RTM.

Also try out ASP.NET 5 with Visual Studio Code on Windows, Mac and Linux!

You can find documentation and samples for ASP.NET 5 at http://docs.asp.net.

You can find details on the new features and bug fixes in beta6 for the following components on their corresponding release pages:

Breaking Changes

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

Known Issues

  • Tooling known issues Please see the Known Issues list in the Tooling repo
  • "The current runtime target framework is not compatible" error when running on IIS or IIS Express To target dnx46 or dnx452 when running on IIS or IIS Express set the DNX_IIS_RUNTIME_FRAMEWORK environment variable to the target framework that you want to use (dnx46 or dnx452). You can do this from within Visual Studio in the Project Properties page for the web application, on the Debug tab. Just choose the IIS Express profile and add the environment variable.
Assets 2

beta5

30 Jun 21:09
@danroth27 danroth27
v1.0.0-beta5
8106fc8
Compare
Choose a tag to compare
beta5 Pre-release
Pre-release

ASP.NET 5 Beta5 Release Notes

We are please to announce the release of ASP.NET 5 beta5! ASP.NET 5 beta5 ships publicly as NuGet packages on https://nuget.org and is supported by Visual Studio 2015.

Also try out ASP.NET 5 with Visual Studio Code on Windows, Mac and Linux!

You can find documentation and samples for ASP.NET 5 at http://docs.asp.net.

You can find details on the new features and bug fixes in beta5 for the following components on their corresponding release pages:

Breaking Changes

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

Known Issues

  • Tooling known issues Please see the Known Issues list in the Tooling repo for issues with the ASP.NET 5 and DNX tooling in Visual Studio 2015.
  • Packages not resolved by Ctrl-. after updating to beta5 Not all beta5 packages are correctly indexed by the Ctrl-. feature in Visual Studio 2015 RC due to package format changes. This issue will be resolved in a future tooling release.
  • Removed ActivateAttribute causes Razor editor errors When using the Razor editor in Visual Studio 2015 RC you may see build errors due to the removal of the ActivateAttribute. You can work around this issue by adding a stub ActivateAttribute class to your project.
  • Kestrel does not shutdown gracefully When using Ctrl-C to shutdown kestrel it does not shutdown cleanly. To work around this issue use Ctrl-Z to send the process to the background and then kill the process.
  • Restoring packages occasionally fails on Mono due to request timeouts Package restore sometimes fails on Mono due to request timeouts. This issue is being investigated and will be resolved in a future release.
  • **EF reverse engineering does not work on Core CLR** The dnx . ef RevEng command will fail with the following error if you attempt to use it when running under Core CLR. This issue occurs because Beta5 does not include an assembly for dnxcore50 for the EntityFramework.SqlServer.Design package, so even though dnu restore may appear to work, it is actually missing. 
System.IO.FileNotFoundException: Could not load file or assembly ‘EntityFramework.SqlServer.Design’

The solution to this issue if to run the command under full .NET. You can swap to full .NET by running the following command.

dnvm use 1.0.0-beta5 –r clr
Assets 2

beta4

01 May 04:43
@danroth27 danroth27
v1.0.0-beta4
ccffee8
Compare
Choose a tag to compare
beta4 Pre-release
Pre-release

ASP.NET 5 Beta4 Release Notes

We are please to announce the release of ASP.NET 5 beta4! ASP.NET 5 beta4 ships publicly as NuGet packages on https://nuget.org and is included with Visual Studio 2015.

Try out ASP.NET 5 with Visual Studio Code on Windows, Mac and Linux!

You can find details on the new features and bug fixes in beta4 for the following components on their corresponding release pages:

Breaking Changes

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

Known Issues

  • Tooling known issues Please see the Known Issues list in the Tooling repo for issues with the ASP.NET 5 and DNX tooling in Visual Studio 2015.
  • DNVM uses wrong DNX feed by default The .NET Version Manager (DNVM) that ships with Visual Studio 2015 RC is pointing to the incorrect DNX feed. To work around this issue and point DNVM at the official NuGet feed on https://www.nuget.org set the DNX_FEED environment variable to https://www.nuget.org/api/v2
  • NuGet v3 feed not supported ASP.NET 5 and DNX do not currently support the NuGet v3 feed (https://api.nuget.org/v3/index.json) and if this feed is enabled in your package sources then package restore may fail. To work around this issue disable the NuGet v3 feed from your package sources and use the NuGet v2 feed (https://www.nuget.org/api/v2) instead.
  • DNX pins a version of the .NET Compiler Platform ("Roslyn") that does not match the official rc2 version The beta4 version of DNX contains and loads an older version of the .NET Compiler Platform ("Roslyn") assemblies that are not fully compatible with the publicly released rc2 version. This issue will be addressed in a future release.
  • Add Service Reference is not yet supported in ASP.NET 5 applications The most common way to communicate with an existing WCF service from an app is to use “Add Service Reference” to generate client code you can call. However, this functionality is not yet supported for ASP.NET 5 applications. As a workaround you can create a temporary Windows 8.1 Universal app, use Add Service Reference there, and manually copy the generated references.cs file into the ASP.NET 5 application.
  • Package restore does not fully resolve WCF dependencies If you create a new ASP.NET 5 application and add WCF package references, the app will not compile because several other package references are missing. This is due to a bug in the way package dependencies are resolved. You can work around the issue by manually editing project.json and adding the missing dependencies:
    • System.Runtime": "4.0.20-beta-22816",
    • System.Runtime.Extensions": "4.0.10-beta-22816",
    • System.Diagnostics.Debug": "4.0.10-beta-22816",
    • System.Text.Encoding": "4.0.10-beta-22816",
    • System.Collections.Specialized": "4.0.0-beta-22816",
    • System.Diagnostics.Contracts": "4.0.0-beta-22816",
    • System.Linq.Queryable": "4.0.0-beta-22816",
    • System.Net.Http": "4.0.0-beta-22816",
    • System.Net.NameResolution": "4.0.0-beta-22816",
    • System.Net.Security": "4.0.0-beta-22816",
    • System.Net.WebHeaderCollection": "4.0.0-beta-22816",
    • System.Reflection.DispatchProxy": "4.0.0-beta-22816",
    • System.Runtime.Serialization.Xml": "4.0.10-beta-22816",
    • System.Runtime.Serialization.Primitives": "4.0.10-beta-22816",
    • System.Security.Cryptography.Hashing": "4.0.0-beta-22816",
    • System.Xml.XmlDocument": "4.0.0-beta-22816",
    • System.ServiceModel.Http": "4.0.10-beta-22816",
    • System.ServiceModel.NetTcp": "4.0.0-beta-22816",
    • System.ServiceModel.Primitives": "4.0.0-beta-22816"
Assets 2

beta3

23 Mar 20:30
@danroth27 danroth27
v1.0.0-beta3
8ec209d
Compare
Choose a tag to compare
beta3 Pre-release
Pre-release

ASP.NET 5 Beta3 Release Notes

You can find details on the new features and bug fixes in beta3 for the following components on their corresponding release pages:

Known Issues

A bug in the .NET Core version of the ADO.NET provider for SQL Server prevents it from working on Windows 7 and Windows Server 2008 R2 (aspnet/EntityFramework#1545)
This blocks using Entity Framework against a SQL Server database on .NET Core (aspnetcore50) in those operating systems. The main symptom is the error “System.DllNotFoundException : Unable to load DLL 'sni.dll': procedure could not be found. (Exception from HRESULT: 0x8007007F)”. Currently the only workaround is to run on the full .NET Framework (aspnet50).

Assets 2

beta2

16 Jan 15:09
@danroth27 danroth27
v1.0.0-beta2
399249c
Compare
Choose a tag to compare
beta2 Pre-release
Pre-release

ASP.NET 5 Beta2 Release Notes

You can find details on the new features and bug fixes in beta2 for the following components on their corresponding release pages:

Known Issues

There are no known issues at this time.

Assets 2

beta1

12 Nov 15:32
@danroth27 danroth27
v1.0.0-beta1
88ec280
Compare
Choose a tag to compare
beta1 Pre-release
Pre-release

ASP.NET vNext is now ASP.NET 5!

You can find details on the new features and bug fixes in beta1 at the corresponding release pages for the following ASP.NET 5 components:

Known issues

  • Running Kestrel on Windows 8.1 without Visual Studio 2015 installed results in an error "The program can't start because MSVCR120.dll is missing from your computer." This is a temporary issue that will be resolved in a future release. Install Visual Studio 2015 to work around the issue.
Assets 2

alpha4

06 Oct 17:09
@danroth27 danroth27
v1.0.0-alpha4
afde097
Compare
Choose a tag to compare
alpha4 Pre-release
Pre-release

You can find details on the new features and bug fixes in alpha4 at the corresponding release pages for the following ASP.NET vNext components:

Known issues

  • ASP.NET scenarios on the Core CLR version of the KRE are not currently functional on Windows 7 or Windows 2008 R2. This is a temporary issue that will be addressed in the next preview release.
Assets 2