Description
AspNetCoreModule V1 removed from Windows Hosting Bundle
Windows Hosting Bundle wouldn't contain AspNetCoreModule V1 in 3.0 release.
AspNetCoreModuleV2 is backwards compatible with AspNetCoreModule OutOfProcess and is recommended for use with ASP.NET Core 3.0 applications.
Please discuss this on dotnet/aspnetcore#7095
Version introduced
3.0
Old behavior
AspNetCoreModule V1 was in Windows Hosting Bundle
New behavior
AspNetCoreModule V1 removed from Windows Hosting Bundle
Reason for change
AspNetCoreModuleV2 is backwards compatible with AspNetCoreModule OutOfProcess and is recommended for use with ASP.NET Core 3.0 applications.
Recommended action
Use AspNetCoreModuleV2 with ASP.NET Core 3.0 applications.
If AspNetCoreModule V1 is required it can be installed using 2.1/2.2 Windows Hosting Bundle.
This would break 3.0 applications that explicitly opted into using AspNetCoreModule V1 using <AspNetCoreModuleName>AspNetCoreModule</AspNetCoreModuleName> or ones having custom web.config with <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
Category
- ASP.NET Core
Affected APIs
"Not detectable via API analysis"
Issue metadata
- Issue type: breaking-change