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"