blazor-lazy-loading
blazor-lazy-loading copied to clipboard
Support new .NET 5 lazy assembly loader
Blazor team did a lot of work to introduce a partial implementation of the lib into blazor itself. This means that the LazyAssemblyLoader
is a native part of blazor now! When .NET 5 RC1 is released, this library should shrink and reuse as much as it can from the official lazy loading support.
Has there been any movement on this at all? I've been looking at this library as a way to help modularize a set of apps into Blazor and if it's using the native Blazor lazy loading that would be cool. This lib seems super easy to configure and use so I would love to start prototyping with it.
No movement cause R1 was super buggy. Now that they released R2 I'll give it another go and hopefully adapt the library to it :)
Had some time to look into this, some bits of the metadata generation are broken and need to investigate the .net5 internals to make it work. Will take some time. If anyone wants to contribute i can push my changes and coordinate.
If anyone wants
I'm want)
Hi @isc30 - just a quick check whether you already know when you could have the .NET5-based new version available? Thanks for the great lib!
Hi, I'm super busy lately but this is top in my priority list. I didn't manage to make it work yet but im optimistic :)
:-)
Sorry for disturbing again. Maybe you have a remote idea of when the ETA of this update might be? 😇 @isc30
Hi, since stable .net5 was released some days ago, I'm working on making it work for that specific version. I expect to have it by this week.
WIP in branch feature/net5
https://github.com/isc30/blazor-lazy-loading/compare/feature/net5
Blocked by the following error when trying to execute the custom MsBuild Task: GenerateManifest
any ideas if net5.0
target dlls can contain msbuild Tasks?
Tried if porting only the components project to .net5
would help with the msbuild task issue but nothing.
After some days of fighting with this I'm out of ideas on how to make a custom MsBuild task work in .net5
.....
There are 2 approaches I tried:
- Porting everything to net5.0:
feature/net5
- Porting only blazor libraries to net5.0:
feature/net5.0-only-components
Both suffer from the same error I mentioned before.
When this gets fixed, missing work is to:
- [ ] Implement a new
LazyRouter
that wraps the new<Router>
and hooks into the newOnNavigateAsync
andNavigating
- [ ] Change
AssemblyLoader
internals to use the newLazyAssemblyLoader
instead of doing the locate+fetch itself
Did you ask over at the .NET Core repo? They are quite helpful, usually.
No, I didn't reach them. I will be trying using NestedTask
this afternoon and will reach them if it doesn't work.
If you want to help, the easiest way is to checkout feature/net5.0-only-components
, build BlazorLazyLoading.sln
and then build demo/Demo.sln
to see the error. If we manage to sort this out, the rest of the implementation is quite straightforward.
Please make sure you use the stable net5.0.0 sdk
I'll be available in https://gitter.im/Blazor-Lazy-Loading/community