Description
The section which describes the use of WasmApplicationEnvironmentName makes no declaration that the previous 'Blazor-Environment' response header is no longer used.
Nor is it listed as a breaking change here: https://learn.microsoft.com/en-us/aspnet/core/breaking-changes/10/overview?view=aspnetcore-10.0
Page URL
https://learn.microsoft.com/en-us/aspnet/core/migration/90-to-100?view=aspnetcore-10.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/migration/90-to-100.md
Document ID
ec188d75-0a05-2029-be73-b227980fac06
Platform Id
d5dc8b7b-be8c-9338-e3df-4401484986e9
Article author
@wadepickett
Metadata
- ID: ec188d75-0a05-2029-be73-b227980fac06
- PlatformId: d5dc8b7b-be8c-9338-e3df-4401484986e9
- Service: aspnet-core
- Sub-service: migration
Description
The section which describes the use of
WasmApplicationEnvironmentNamemakes no declaration that the previous 'Blazor-Environment' response header is no longer used.Nor is it listed as a breaking change here: https://learn.microsoft.com/en-us/aspnet/core/breaking-changes/10/overview?view=aspnetcore-10.0
Page URL
https://learn.microsoft.com/en-us/aspnet/core/migration/90-to-100?view=aspnetcore-10.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/migration/90-to-100.md
Document ID
ec188d75-0a05-2029-be73-b227980fac06
Platform Id
d5dc8b7b-be8c-9338-e3df-4401484986e9
Article author
@wadepickett
Metadata