beta5

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:

• Caching
• Configuration
• CORS
• DataProtection
• DependencyInjection
• Diagnostics
• dnvm
• dnx
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KestrelHttpServer
• Localization
• Logging
• Microsoft.Data.Sqlite
• Mvc
• Options
• Razor
• Routing
• Scaffolding
• Security
• Session
• SignalR-Server
• StaticFiles
• Testing
• UserSecrets
• WebSockets

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

beta4

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:

• Caching
• Configuration
• CORS
• DataProtection
• DependencyInjection
• Diagnostics
• dnvm
• dnx
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KestrelHttpServer
• Logging
• Mvc
• Options
• Razor
• Routing
• Scaffolding
• Security
• Session
• StaticFiles
• Testing
• UserSecrets
• WebSockets

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"

beta3

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:

• Caching
• Configuration
• DataProtection
• DependencyInjection
• Diagnostics
• dotnetsdk
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KestrelHttpServer
• Logging
• Mvc
• Options
• Razor
• Routing
• Scaffolding
• Security
• SignalR-Server
• StaticFiles
• WebSocketAbstractions
• WebSockets
• XRE

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

beta2

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:

• Caching
• Configuration
• DataProtection
• DependencyInjection
• Diagnostics
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KestrelHttpServer
• KRuntime
• kvm
• Logging
• Mvc
• Options
• Razor
• Routing
• Scaffolding
• Security
• SignalR-Server
• StaticFiles
• WebSocketAbstractions
• WebSockets

Known Issues

There are no known issues at this time.

beta1

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:

• Caching
• Configuration
• DataCommon.SQLite
• DataCommon
• DataProtection
• DependencyInjection
• Diagnostics
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KestrelHttpServer
• KRuntime
• Logging
• MVC
• Options
• Razor
• Routing
• Security
• SignalR-Server
• StaticFiles
• WebSocketsAbstractions
• WebSockets

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.

alpha4

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:

• Caching
• Configuration
• DataCommon.SQLite
• DataCommon
• DataProtection
• DependencyInjection
• Diagnostics
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KestrelHttpServer
• KRuntime
• Logging
• MVC
• Options
• Razor
• Routing
• Security
• SignalR-Server
• StaticFiles
• WebSocketsAbstractions
• WebSockets

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.

alpha3

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

• Caching
• Configuration
• DataCommon.SQLite
• DataCommon
• DataProtection
• DependencyInjection
• Diagnostics
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KestrelHttpServer
• KRuntime
• Logging
• MVC
• Options
• Razor
• Routing
• Security
• SignalR-Server
• StaticFiles
• WebSocketsAbstractions
• WebSockets

Known issues

• When using Core CLR on X64 platform (X64 + SVRC50) you may see a CompilationFailedException when using Razor views or a EntryPointNotFoundException when adding ASP.NET Identity authentication services for SQL Server. Please choose a different platform configuration when using these scenarios. See details for the related issues here: MVC#846, Identity#157.
• If you upgrade a previous Visual Studio installation to CTP3, when you try to publish your app you might encounter a publishing dialog box where you cannot select an existing website or the “New” button. To work around this issue delete the following assemblies from the ~\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies folder:
  • Microsoft.VisualStudio.Web.WindowsAzure.Contracts.dll
  • Microsoft.VisualStudio.Web.WindowsAzure.Explorer.dll
  • Microsoft.VisualStudio.Web.Internal.Contracts.dll
• To publish applications using SQL Server (e.g. MVCMusicStore App) to Azure you need to enable MARS for your connection string. Otherwise, you will get InvalidOperationException when browsing to check out an Album. See detailed issue here: EntityFramework#529.
• If you upgrade from a previous Visual Studio CTP release to CTP3, you need to refresh the project.json schema cached by previous Visual studio install to get the latest schema. To do this, after you create a ASP.Net vNext project via Visual Studio IDE, open “project.json” file, and change the URL on the top from http://www.asp.net/media/4878834/project.json to http://www.asp.net/media/4878834/project.json?reload and press enter to refresh the schema.
• When doing “KPM restore” or running ASP.Net vNext application on Windows Server 2008 R2 with Core CLR, you might encounter System.TypeLoadException. Please choose a different OS platform to try out Core CLR on CTP3. See detailed issue report here: KRunTime#517

alpha2

ASP.NET vNext

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

• Configuration
• DataCommon.SQLite
• DataCommon
• DataProtection
• DependencyInjection
• Diagnostics
• EntityFramework
• FileSystem
• Hosting
• HttpAbstractions
• Identity
• KRuntime
• Logging
• MVC
• Options
• Razor
• Routing
• Security
• SignalR-Server
• StaticFiles
• WebSocketAbstractions
• WebSockets

.NET APIs

The following core .NET API contracts were added for this release

• System.ComponentModel.Annotations
• System.IO.Pipes
• System.Net.Http
• System.Runtime.CompilerServices.VisualC
• System.Runtime.Serialization.Xml

System.Net.Http

The System.Net.Http package in this release contains the HttpClient API surface area but lacks a message handler implementation needed to send HTTP requests. You can find a WinHTTP based message handler implementation in the System.Net.Http.WinHttpHandler package on the ASP.NET vNext dev MyGet feed.

The goal for this new WinHttpHandler is to provide higher performance and scalability than the existing handlers, HttpClientHandler/WebRequestHandler, which are based on the HttpWebRequest protocol stack. This new handler is preliminary and subject to further iterations in terms of API design, functionality, performance tuning and naming as we receive feedback from internal and external developers.

The current version of the API surface spans the following aspects of HTTP:

• Sending HTTP requests and receiving a response, including https:// URLs
• Setting automatic redirection policy
• Enable/disable usage of cookies
• Basic SSL and ability to ignore some server certificate validation errors
• Proxy settings
• Timeouts for connecting, sending and receiving.
• Server and Proxy authentication (Anonymous, Basic, Digest, NTLM, Kerberos and Negotiate)

Note: Not all of the above APIs have been completely implemented yet. Future versions of WinHttpHandler will include a more complete implementation of the above API surface and may introduce changes in naming and/or API design.