Core.AspNet.Web.WebPages.Base
1.0.0.26263
dotnet add package Core.AspNet.Web.WebPages.Base --version 1.0.0.26263
NuGet\Install-Package Core.AspNet.Web.WebPages.Base -Version 1.0.0.26263
<PackageReference Include="Core.AspNet.Web.WebPages.Base" Version="1.0.0.26263" />
<PackageVersion Include="Core.AspNet.Web.WebPages.Base" Version="1.0.0.26263" />
<PackageReference Include="Core.AspNet.Web.WebPages.Base" />
paket add Core.AspNet.Web.WebPages.Base --version 1.0.0.26263
#r "nuget: Core.AspNet.Web.WebPages.Base, 1.0.0.26263"
#:package Core.AspNet.Web.WebPages.Base@1.0.0.26263
#addin nuget:?package=Core.AspNet.Web.WebPages.Base&version=1.0.0.26263
#tool nuget:?package=Core.AspNet.Web.WebPages.Base&version=1.0.0.26263
Core.AspNet.Web.WebPages
System.Web.WebPages — the Web Pages 2 runtime: the WebPage base class, layouts and sections,
@Html helpers, validation, and standalone .cshtml routing.
<PackageReference Include="Core.AspNet.Web.WebPages.Base" Version="1.0.0" />
Add Core.AspNet.Web.WebPages.Razor and Core.AspNet.Web.WebPages.Deployment alongside it for
runtime-compiled .cshtml. Core.AspNet.Web.Mvc brings all of them.
Assembly vs package name. The package is
Core.AspNet.Web.WebPages.Base; the assembly inside it isCore.Web.WebPages. .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 works
- Standalone
.cshtmlpages, extensionless URLs and the default document - Layouts,
@RenderBody,@RenderSection,@RenderPage, thePagedictionary @Html.*helpers, automatic HTML encoding,IHtmlString- Underscore-prefixed files refused, as the framework always did
- Self-posting forms,
IsPost,Request.Unvalidated - Display modes (
DisplayModeProvider) for mobile and device-specific views
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.Web.Forms (>= 1.0.0.26263)
- Core.AspNet.Web.Infrastructure (>= 1.0.0.26263)
- Core.AspNet.Web.Razor (>= 1.0.0.26263)
- Core.AspNet.Web.WebPages.Deployment (>= 1.0.0.26263)
- System.Configuration.ConfigurationManager (>= 8.0.0)
-
net6.0
- Core.AspNet.Web.Forms (>= 1.0.0.26263)
- Core.AspNet.Web.Infrastructure (>= 1.0.0.26263)
- Core.AspNet.Web.Razor (>= 1.0.0.26263)
- Core.AspNet.Web.WebPages.Deployment (>= 1.0.0.26263)
- System.Configuration.ConfigurationManager (>= 8.0.0)
-
net8.0
- Core.AspNet.Web.Forms (>= 1.0.0.26263)
- Core.AspNet.Web.Infrastructure (>= 1.0.0.26263)
- Core.AspNet.Web.Razor (>= 1.0.0.26263)
- Core.AspNet.Web.WebPages.Deployment (>= 1.0.0.26263)
- System.Configuration.ConfigurationManager (>= 8.0.0)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Core.AspNet.Web.WebPages.Base:
| Package | Downloads |
|---|---|
|
Core.AspNet.Web.WebPages.Razor
The build provider that hands a .cshtml to Razor and its output to the compiler. Required for any application that renders Razor views. |
|
|
Core.AspNet.Web.Mvc
ASP.NET MVC 4 on .NET 10 - controllers, Razor v2 views, model binding, TempData and async actions, plus [Route] attribute routing supplied by this port. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.0.0.26263 | 51 | 9/20/2026 |
| 1.0.0.26262 | 49 | 9/19/2026 |