Skip to content

Publish minified .js files as a package, remove related components from Shared Framework #56934

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

Open
wtgodbe opened this issue Jul 22, 2024 · 2 comments
Assignees
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Comments

@wtgodbe
Copy link
Member

wtgodbe commented Jul 22, 2024

We should pull the minified .js files & their related components out of the Shared Framework, and instead distribute them as an out-of-band runtime pack that will be available in the Visual Studio offline package cache - this is what the WebAssembly SDK already does for their JS components, and should make it much easier to build aspnetcore as part of offline source-build in the VMR. CC @javiercn in case I'm missing any details.

@wtgodbe wtgodbe added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jul 22, 2024
@wtgodbe wtgodbe added this to the .NET 10 Planning milestone Jul 22, 2024
@wtgodbe wtgodbe self-assigned this Jul 22, 2024
@drsa353
Copy link

drsa353 commented Jul 22, 2024

Blazor is great but it needs to be more object oriented and there are a lot of Un-logical issues in control event handling that should be solved

@wtgodbe
Copy link
Member Author

wtgodbe commented May 2, 2025

@javiercn can this be closed now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

No branches or pull requests

2 participants