Core.AspNet.Net.Http.Formatting
1.0.0.26263
dotnet add package Core.AspNet.Net.Http.Formatting --version 1.0.0.26263
NuGet\Install-Package Core.AspNet.Net.Http.Formatting -Version 1.0.0.26263
<PackageReference Include="Core.AspNet.Net.Http.Formatting" Version="1.0.0.26263" />
<PackageVersion Include="Core.AspNet.Net.Http.Formatting" Version="1.0.0.26263" />
<PackageReference Include="Core.AspNet.Net.Http.Formatting" />
paket add Core.AspNet.Net.Http.Formatting --version 1.0.0.26263
#r "nuget: Core.AspNet.Net.Http.Formatting, 1.0.0.26263"
#:package Core.AspNet.Net.Http.Formatting@1.0.0.26263
#addin nuget:?package=Core.AspNet.Net.Http.Formatting&version=1.0.0.26263
#tool nuget:?package=Core.AspNet.Net.Http.Formatting&version=1.0.0.26263
Core.AspNet.Net.Http.Formatting
System.Net.Http.Formatting — the media-type formatters Web API negotiates with.
<PackageReference Include="Core.AspNet.Net.Http.Formatting" Version="1.0.0" />
You rarely reference this directly; it arrives with Core.AspNet.Web.Http.
Assembly vs package name. The package is
Core.AspNet.Net.Http.Formatting; the assembly inside it isCore.Net.Http.Formatting. .NET ships an emptySystem.Web.dllfacade inMicrosoft.NETCore.Appand the host gives the shared framework precedence, so an app-localSystem.Web.dllis never loaded — the port therefore cannot use the original assembly names. Namespaces are unchanged, so your code andInherits=attributes are unaffected; onlyweb.configentries that name an assembly need updating.
What is inside
MediaTypeFormatterand the JSON, XML and form-url-encoded implementationsHttpContentExtensions—ReadAsAsync<T>,ReadAsFormDataAsyncFormDataCollection,MediaTypeHeaderValueExtensions, the formatter collection
Json.NET
JsonMediaTypeFormatter is built on Json.NET, whose source is compiled directly into this
assembly rather than referenced as a package. That keeps the port diffable against the upstream tree
it came from and avoids a version conflict with whatever Json.NET your own application uses — the
types are internal to this assembly and never appear in its public surface.
Documentation
PORTING-GUIDE.md (step-by-step migration from IIS) and LIMITATIONS.md (what differs from ASP.NET
on .NET Framework, and why) ship in the repository.
Licence
Apache-2.0 AND MIT. Microsoft released the ASP.NET Web Stack - the sources this is built
from - under the Apache License 2.0. Mono's AssemblyInfo.cs and the code written for this port
are MIT. Both are permissive and compatible; the compound expression means the assembly contains
code under both, not that you may pick one. THIRD-PARTY-NOTICES.md ships in the package and
says which part is which.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Core.AspNet.Configuration (>= 1.0.0.26263)
- Newtonsoft.Json (>= 13.0.3)
- System.Configuration.ConfigurationManager (>= 8.0.0)
-
net6.0
- Core.AspNet.Configuration (>= 1.0.0.26263)
- Newtonsoft.Json (>= 13.0.3)
- System.Configuration.ConfigurationManager (>= 8.0.0)
-
net8.0
- Core.AspNet.Configuration (>= 1.0.0.26263)
- Newtonsoft.Json (>= 13.0.3)
- System.Configuration.ConfigurationManager (>= 8.0.0)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Core.AspNet.Net.Http.Formatting:
| Package | Downloads |
|---|---|
|
Core.AspNet.Web.Http.WebHost
Hosts ASP.NET Web API inside the ported System.Web pipeline, so .aspx pages and API controllers serve from one application. |
|
|
Core.AspNet.Web.Http.Library
ASP.NET Web API on .NET 10 - ApiController, attribute and convention routing, content negotiation, and JSON and XML formatters. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.0.0.26263 | 43 | 9/20/2026 |
| 1.0.0.26262 | 47 | 9/19/2026 |