Closed SteveSandersonMS closed 3 years ago
@SteveSandersonMS Thank you for your reporting!
And, I appreciate your very kind comment. 👍
Because of your comment in this thread, I could reproduce the problem, and I could fix it at commit 090df430 in the net5.0
branch in this repository.
Finally, I published the latest fixed version of the HeadElement
NuGet package.
Again, thank you for your contribution!
Also thanks to you @jsakamoto for producing this package!
Starting with .NET 5 RC1, there's a binary-breaking change in
RenderTreeFrame
that will affect this library because of how it uses the internalRenderTreeFrame
APIs. For this library to work with .NET 5 RC1 and later, you'll need to recompile. And because you're using theMicrosoft.AspNetCore.Components.RenderTree.*
APIs directly you'll have to multitargetnetstandard2.0
andnet5.0
if you want to retain compatibility with both.I think this line here would need to be changed to:
... and then instead of depending purely on
Microsoft.AspNetCore.Components.Web
3.0.0 directly, you'll need to depend on either the 3.x or 5.x versions depending on target framework. For example, replace this line here with something like: