Core.AspNet.Web.Infrastructure 1.0.0.26263

dotnet add package Core.AspNet.Web.Infrastructure --version 1.0.0.26263
                    
NuGet\Install-Package Core.AspNet.Web.Infrastructure -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.Infrastructure" 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.Infrastructure" Version="1.0.0.26263" />
                    
Directory.Packages.props
<PackageReference Include="Core.AspNet.Web.Infrastructure" />
                    
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.Infrastructure --version 1.0.0.26263
                    
#r "nuget: Core.AspNet.Web.Infrastructure, 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.Infrastructure@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.Infrastructure&version=1.0.0.26263
                    
Install as a Cake Addin
#tool nuget:?package=Core.AspNet.Web.Infrastructure&version=1.0.0.26263
                    
Install as a Cake Tool

Core.AspNet.Web.Infrastructure

Microsoft.Web.Infrastructure — a small support assembly the ASP.NET Web Stack depends on for dynamic module registration.

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

You almost certainly do not reference this directly; it arrives with Core.AspNet.Web.WebPages.Base and Core.AspNet.Web.Mvc, which need it.

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

What is inside

Microsoft.Web.Infrastructure.DynamicModuleHelper.DynamicModuleUtility — the helper Web Pages and MVC use to register an IHttpModule from a PreApplicationStartMethod rather than from web.config.

It is tiny, and exists as its own package only because that is how upstream factored it and because the Web Stack assemblies reference it by name.

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.Web.Infrastructure:

Package Downloads
Core.AspNet.Web.WebPages.Deployment

Web Pages version resolution and deployment support. Arrives with AspNetCore.Web.WebPages.Base; you do not reference it directly.

Core.AspNet.Web.WebPages.Base

ASP.NET Web Pages on .NET 10 - standalone .cshtml rendering, layouts, sections, @model and the @Html helpers, with extensionless routing.

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.

Net4x.WebLibrary

Web Library Fundamental Class

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.0.0.26263 0 9/20/2026
1.0.0.26262 40 9/19/2026