[Announcement] Updates

[galvesribeiro]

Hello folks, happy new year to everyone!

I know many of you are upset that the components are not being kept up-to-date with the latest releases of Blazor.

The bigger reason for that, is because Blazor changed drastically the way it deals with static content like CSS and JS, and also because I'm with a very limited time for my OSS projects recently. That change on Blazor removed our ability to inject static content when referencing a Nuget package asking the developer to manually add the links to those resources on the target project. We think that it is far from ideal, and none of the Web/Client frameworks we've seeing Today as the developers to do so.

I've being researching with @attilah multiple ways of doing this right and we're close to get to a point where this limitation will be breached. To give an idea, I'm still using older versions of Blazor on production applications so I can keep using the components.

I'll come up with an update here ASAP although I can't promise a precise date for it. Rest assured that I'm suffering from it the same way as you do, specially because .Net Core 2.2 is now EOL.

Thanks!

[szmalec]

@galvesribeiro
Do you think that the solution / workaround for the problem of static assets used in Tewr/BlazorFileReader or in Toolbelt.Blazor.LoadingBar is OK?

[knight1219]

Any news on this?