Core.AspNet.Web.Extensions
1.0.0.26263
dotnet add package Core.AspNet.Web.Extensions --version 1.0.0.26263
NuGet\Install-Package Core.AspNet.Web.Extensions -Version 1.0.0.26263
<PackageReference Include="Core.AspNet.Web.Extensions" Version="1.0.0.26263" />
<PackageVersion Include="Core.AspNet.Web.Extensions" Version="1.0.0.26263" />
<PackageReference Include="Core.AspNet.Web.Extensions" />
paket add Core.AspNet.Web.Extensions --version 1.0.0.26263
#r "nuget: Core.AspNet.Web.Extensions, 1.0.0.26263"
#:package Core.AspNet.Web.Extensions@1.0.0.26263
#addin nuget:?package=Core.AspNet.Web.Extensions&version=1.0.0.26263
#tool nuget:?package=Core.AspNet.Web.Extensions&version=1.0.0.26263
Core.AspNet.Web.Extensions
System.Web.Extensions — ASP.NET AJAX: ScriptManager, UpdatePanel, page methods, and the
client-script bridge to [WebMethod] endpoints.
<PackageReference Include="Core.AspNet.Web.Extensions" Version="1.0.0" />
It arrives automatically with Core.AspNet.Web.Hosting.Kestrel. A missing reference is not a compile
error — it shows up as every request returning 500 once a page uses a ScriptManager.
Assembly vs package name. The package is
Core.AspNet.Web.Extensions; the assembly inside it isCore.Web.Extensions. .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
ScriptManager,ScriptManagerProxy,ScriptReferenceUpdatePanel,UpdateProgress,Timer— including the length-prefixed partial-rendering delta protocol that async postbacks use- Page methods and
[ScriptService].asmxservices returning{"d": ...} System.Web.Script.Serialization.JavaScriptSerializer
The Microsoft AJAX client library is embedded under the exact names the upstream build gave it,
because ScriptReferenceBase cross-checks every [assembly: WebResource] declaration against a real
embedded resource and throws if one is missing.
This package needs Core.AspNet.Web.Services, because the client-script bridge is built on
WebMethodAttribute and WebServiceHandlerFactory.
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 | 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.Services (>= 1.0.0.26263)
- System.Configuration.ConfigurationManager (>= 8.0.0)
- System.Drawing.Common (>= 8.0.0)
-
net6.0
- Core.AspNet.Web.Forms (>= 1.0.0.26263)
- Core.AspNet.Web.Services (>= 1.0.0.26263)
- System.Configuration.ConfigurationManager (>= 8.0.0)
- System.Drawing.Common (>= 8.0.0)
-
net8.0
- Core.AspNet.Web.Forms (>= 1.0.0.26263)
- Core.AspNet.Web.Services (>= 1.0.0.26263)
- System.Configuration.ConfigurationManager (>= 8.0.0)
- System.Drawing.Common (>= 8.0.0)
NuGet packages (5)
Showing the top 5 NuGet packages that depend on Core.AspNet.Web.Extensions:
| Package | Downloads |
|---|---|
|
Starb.HtmlEditor
Basic Edition, ASP.NET 2.0 |
|
|
Core.AspNet.Web.DynamicData
ASP.NET Dynamic Data on .NET 10 - scaffolded list, detail and edit pages driven by your model, running on IQueryable or EF Core instead of LINQ to SQL. |
|
|
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. |
|
|
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. |
|
|
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 | 41 | 9/19/2026 |