-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Stop shipping Blazor WASM templates in 3.1 patches #28492
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
Conversation
@dotnet/aspnet-build are there any known issues with the mac checks on release/3.1? Its failed for me since yesterday |
Yeah, that's https://github.com/dotnet/core-eng/issues/11636 |
@pranavkm should I just go ahead and delete the files now too? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we remove the contents+tests alltogether?
Ok I will update the PR to remove all the content as well now |
Is anyone aware of any files/content that live outside of the project templates directory for these wasm templates? The build is green but...? |
@HaoK AFAIK, template files don't exist outside of the templates for Blazor. |
Hello human! Please make sure you've included the Shiproom Template in a comment or (preferably) the PR description. Also, make sure this PR is not marked as a draft and is ready-to-merge. |
Part of #25923
Description
The Blazor WASM template package is a going to be out of servicing support as of March. This change removes the code so it no longer will be built / shipped. We also plan to deprecate the package on nuget with a custom error message pointing at the current version of the template.
Customer impact
This was the first version of the WASM templates, and there are many fixes and scenarios that are only in 5.0+, the expectation was that most customers will need to upgrade to 5.0 and not remain on 3.2 indefinitely, especially since once out of support, not even security fixes will be ported to 3.2
Regression
No
Risk
Low. We are just removing the entire source directory along with the tests.