Microsoft.AspNetCore.WebUtilities package should be out of Microsoft.AspNetCore.App meta package.
See original GitHub issueMicrosoft.AspNetCore.WebUtilities
package contains the things which can be used in Blazor WebAssembly but it is tightly part of Microsoft.AspNetCore.App
meta-package which can not be referenced to Blazor WebAssembly project. The available version of Microsoft.AspNetCore.WebUtilities
is 2.2.0
which is too old because it is not being updated anymore independently as it has been part of Microsoft.AspNetCore.App
meta-package.
Thank you.
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Migrating the deprecated Microsoft.AspNetCore.Http. ...
I have a .NET 7 Blazor helper library which has been referencing HttpContext from the Microsoft.AspNetCore.Http.Abstractions (2.2.0) nuget.
Read more >Microsoft.AspNetCore.All metapackage for ASP.NET Core ...
This feature requires ASP.NET Core 2.x targeting .NET Core 2.x. Microsoft.AspNetCore.All is a metapackage that refers to a shared framework.
Read more >NETSDK1079: The Microsoft.AspNetCore.All package is ...
In this article. This article applies to: ✔️ .NET Core SDK 3.1.100 and later versions. You may receive this error message when:.
Read more >Microsoft.AspNetCore.App metapackage for ASP.NET Core
The ASP.NET Core shared framework ( Microsoft.AspNetCore.App ) contains assemblies that are developed and supported by Microsoft. Microsoft.
Read more >ASP.NET Core breaking changes for versions 3.0 and 3.1
Lists the breaking changes in ASP.NET Core 3.0 and 3.1.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@guardrex can you update the docs to suggest an alternative approach?
Like using
URLSearchParams
directly via JS interop in this case would be a good alternative.It would be good to have these super low level helpers in then BCL itself