-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server Side Blazor preview 6 #14
Comments
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 ***@***.***> 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
<#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. |
Hi Mike, This is the issue is keep an eye on dotnet/aspnetcore#10986 |
Here’s another good reference dotnet/AspNetCore.Docs#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/
The text was updated successfully, but these errors were encountered: