Core.AspNet.Web.ConfigBridge 1.0.0.26263

.NET 6.0 This package targets .NET 6.0. The package is compatible with this framework or higher. 
dotnet add package Core.AspNet.Web.ConfigBridge --version 1.0.0.26263
                    


                    

                
NuGet\Install-Package Core.AspNet.Web.ConfigBridge -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.Web.ConfigBridge" 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.Web.ConfigBridge" Version="1.0.0.26263" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Core.AspNet.Web.ConfigBridge" />
                    


                            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.Web.ConfigBridge --version 1.0.0.26263
                    


                    

                
#r "nuget: Core.AspNet.Web.ConfigBridge, 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.Web.ConfigBridge@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.Web.ConfigBridge&version=1.0.0.26263
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Core.AspNet.Web.ConfigBridge&version=1.0.0.26263
                    


                            Install as a Cake Tool

Core.AspNet.Web.ConfigBridge

Lets third-party libraries that read System.Configuration.ConfigurationManager see your web.config.

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

It arrives automatically with Core.AspNet.Web.Hosting.Kestrel.

Assembly vs package name. The package is Core.AspNet.Web.ConfigBridge; the assembly inside it is Core.Web.ConfigBridge. .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.

The problem it solves

The port reads configuration through Core.AspNet.Configuration (Mono's implementation). A NuGet library you did not write reads it through the shipping System.Configuration.ConfigurationManager package. Those are two different type sets, and without a bridge the library sees an empty configuration and silently falls back to its defaults — a connection string that is suddenly null, an appSetting that is suddenly missing.

This package installs an IInternalConfigSystem into the shipping package at startup, pointing its GetSection at the ported configuration system. ConfigurationManager.AppSettings and ConnectionStrings then return what web.config says.

How it stays out of trouble

It is the only project compiled against the shipping package's configuration types, and everything crossing its boundary is a primitive or a shared-framework type — so the two System.Configuration.* type sets never meet in one signature.

SetConfigurationSystem is one-shot per process, so the bridge installs once at startup and cannot be reconfigured afterwards.

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 (1)

Showing the top 1 NuGet packages that depend on Core.AspNet.Web.ConfigBridge:

Package Downloads
Core.AspNet.Web.Hosting.Kestrel

Hosts a ported ASP.NET application under Kestrel: app.UseWebForms (), the request adapter, and the MSBuild assets that remove the empty .NET System.Web facade and copy your content files. Start here.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.0.0.26263 88 9/20/2026
1.0.0.26262 90 9/19/2026