This is part of our effort to allow migrating apps targeting .NET Fx / System.Web to .NET Core. We'd like to enable users targeting .NET Framework, and possibly .NET Standard class libraries, to target a library that shims System.Web.HttpContext and related types that are implemented using Microsoft.AspNetCore.Http types. Users could then cross-compile their libraries, referencing these types
and run their apps on .NET Core with minimal changes to existing code.

This issue tracks

• Producing adapter for HttpContext and related types
  • HttpContext (Implement HttpContext against Core HttpContext aspnet/AspLabs#427)
  • HttpRequest (Implement some HttpRequest APIs against core aspnet/AspLabs#435)
  • HttpResponse (Implement HttpRequest against core. aspnet/AspLabs#458)
  • HttpContextBase
  • HttpRequestBase
  • HttpResponseBase
  • HttpServerUtility
  • Items (Implement HttpContext.Items against core aspnet/AspLabs#434)
  • Cache (Implement HttpContext.Cache against core aspnet/AspLabs#443)
  • HttpBrowserCapability
  • Headers (Implement header wrapper for HttpRequest and HttpResponse aspnet/AspLabs#437)
  • Cookies (Implement HttpCookieCollection and HttpCookie aspnet/AspLabs#467)
  • Parameters
  • Form (Enable Form and Query access off of requests aspnet/AspLabs#451)
  • Server Variables (Implement server variables against core aspnet/AspLabs#444)
  • Query (Enable Form and Query access off of requests aspnet/AspLabs#451)
• Producing adapters for filler APIs that are commonly used in .NET Framework apps and libraries e.g. MimeMapping, VirtualPathUtility etc
• Producing a middleware that ensures synthesizes System.Web-like behavior in ASP.NET Core apps.
  • Enable per-endpoint configuration (Buffer input stream for System.Web adapters aspnet/AspLabs#447)
  • Buffer request stream (Buffer input stream for System.Web adapters aspnet/AspLabs#447)
• Adding tests to ensure the implementation is highly compatible.