Core.AspNet.Configuration 1.0.0.26263

dotnet add package Core.AspNet.Configuration --version 1.0.0.26263
                    
NuGet\Install-Package Core.AspNet.Configuration -Version 1.0.0.26263
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Core.AspNet.Configuration" Version="1.0.0.26263" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Core.AspNet.Configuration" Version="1.0.0.26263" />
                    
Directory.Packages.props
<PackageReference Include="Core.AspNet.Configuration" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Core.AspNet.Configuration --version 1.0.0.26263
                    
#r "nuget: Core.AspNet.Configuration, 1.0.0.26263"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Core.AspNet.Configuration@1.0.0.26263
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Core.AspNet.Configuration&version=1.0.0.26263
                    
Install as a Cake Addin
#tool nuget:?package=Core.AspNet.Configuration&version=1.0.0.26263
                    
Install as a Cake Tool

Core.AspNet.Configuration

Mono's System.Configuration, ported to .NET 10. This is what the ported System.Web is written against, and it is not interchangeable with the System.Configuration.ConfigurationManager package.

<PackageReference Include="Core.AspNet.Configuration" Version="1.0.0" />

It arrives automatically with Core.AspNet.Web.Forms; you rarely reference it directly.

Assembly vs package name. The package is Core.AspNet.Configuration; the assembly inside it is Core.Configuration. .NET ships an empty System.Web.dll facade in Microsoft.NETCore.App and the host gives the shared framework precedence, so an app-local System.Web.dll is never loaded — the port therefore cannot use the original assembly names. Namespaces are unchanged, so your code and Inherits= attributes are unaffected; only web.config entries that name an assembly need updating.

Why a separate implementation exists

The ported System.Web depends on Mono's configuration semantics, not merely its API: the config-path model, SaveStart/SaveEnd, FindLocationConfiguration, and friend access to protected internal members. The shipping ConfigurationManager package rejects Mono's WebConfigurationHost outright. Dropping this reference produces roughly 2000 CS0246 errors.

Living beside the real package

System.Configuration.ConfigurationManager still arrives transitively (through System.Data.SqlClient and friends) and its types collide by name with these. WebFormsPort.targets removes that package's compile assets while keeping it deployed, because third-party libraries were compiled against its strong-named identity and nothing else can satisfy them.

If a third-party library reads ConfigurationManager.AppSettings and should see your web.config, add Core.AspNet.Web.ConfigBridge.

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

MIT, as the upstream Mono sources this is built from and the code written for this port. THIRD-PARTY-NOTICES.md ships in the package and says which part is which.

Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (4)

Showing the top 4 NuGet packages that depend on Core.AspNet.Configuration:

Package Downloads
Starb.DataLibrary

Package Description

Starb.PaccoLibrary

Package Description

Core.AspNet.Web.Forms

System.Web for .NET 10 - WebForms pages, server controls, view state, session, caching, membership and output caching, ported from Mono and hosted under Kestrel. The assembly is Core.Web; namespaces are unchanged.

Core.AspNet.Net.Http.Formatting

The System.Net.Http.Formatting types Web API is built on - media-type formatters, content negotiation and the formatter collection.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.0.0.26263 73 9/20/2026
1.0.0.26262 83 9/19/2026
1.0.0.26257 78 9/14/2026