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.