Closed mikes-gh closed 5 years ago
Hi Mike, unfortunately this is only for server-side Blazor projects.
Going forward Razor class libraries will be the way to go for sharing Components and the Blazor class library will die off. But right now Razor class libs don’t work with client-side Blazor.
So it’s swings and roundabouts. I spoke to Dan Roth about this the other day and he said they’re hoping to have it sorted soon.
On Fri, 14 Jun 2019 at 12:59, Mike Surcouf notifications@github.com wrote:
You probably know this already but you can now include static assets in a library which would eliminate a big caveat mentioned in the README
https://devblogs.microsoft.com/aspnet/asp-net-core-and-blazor-updates-in-net-core-3-0-preview-6/
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Blazored/Typeahead/issues/14?email_source=notifications&email_token=ABPCYR3KKY4QID3UJPKSC6TP2OB3BA5CNFSM4HYHF47KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZRHJ7A, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPCYRYWKK2V7WULJZG6XBTP2OB3BANCNFSM4HYHF47A .
Hi Chris
I had a good look round aspnetcore on github and found it difficult to get any info on this. Is it this issue?
Hi Mike,
This is the issue is keep an eye on https://github.com/aspnet/AspNetCore/issues/10986
Here’s another good reference https://github.com/aspnet/AspNetCore.Docs/issues/12884. Looks like preview 9 is the target for RCL to cover client and server scenarios . I feel like I hyjacked your repo for general discussion so feel free to close this.
No worries @mikes-gh 😄
You probably know this already but you can now include static assets in a library which would eliminate a big caveat mentioned in the README
https://devblogs.microsoft.com/aspnet/asp-net-core-and-blazor-updates-in-net-core-3-0-preview-6/