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