-
Notifications
You must be signed in to change notification settings - Fork 132
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
Q: blazor support #1721
Comments
We had a source-build meeting about this a bit ago, @directhex looked into some of the details and I'll try to recap: When you do
However, since runtime packs are downloaded from nuget.org automatically, I would expect the feature to still work when using a source-built SDK. It'll just have to use a Microsoft-built runtime pack. One thing to watch out for is any SDK functionality that might be missing in the source-built SDK that's necessary to apply the runtime pack properly. It seems worthwhile to add a /cc @dleeapho |
Does Microsoft ship this with the SDK?
Is this the mono-based runtime that eventually runs inside the browser?
+1 definitly! |
No, the Microsoft-built SDK can also only acquire runtime packs from nuget.org.
My understanding is it's the Mono runtime compiled via emscripten to run in the browser, plus libraries. This is something I'm less familiar with though. |
It looks like the questions have been answered here. Blazor will be added to 5.0 smoke-tests (#1724). |
@dagood, thank you for clarifying how Blazor fits into the source-build SDK. |
How does blazor support fit into the sdk, and what does it mean for source-build?
Is it something ships out-of-band for source-build SDKs? And for Microsoft SDKs?
@dagood @crummel @dseefeld @omajid @RheaAyase @aslicerh
The text was updated successfully, but these errors were encountered: