Skip to content

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

Merged
merged 3 commits into from
Feb 9, 2021
Merged

Conversation

HaoK
Copy link
Member

@HaoK HaoK commented Dec 7, 2020

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.

@ghost ghost added the area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates label Dec 7, 2020
@SteveSandersonMS SteveSandersonMS changed the title Stop shipping Blazor WASM templates Stop shipping Blazor WASM templates in 3.1 patches Dec 8, 2020
@HaoK
Copy link
Member Author

HaoK commented Dec 8, 2020

@dotnet/aspnet-build are there any known issues with the mac checks on release/3.1? Its failed for me since yesterday

@wtgodbe
Copy link
Member

wtgodbe commented Dec 8, 2020

Yeah, that's https://github.com/dotnet/core-eng/issues/11636

@HaoK HaoK requested review from pranavkm and a team December 9, 2020 20:54
@HaoK HaoK marked this pull request as ready for review December 9, 2020 20:54
@HaoK HaoK requested a review from ryanbrandenburg as a code owner December 9, 2020 20:54
@HaoK
Copy link
Member Author

HaoK commented Dec 9, 2020

@pranavkm should I just go ahead and delete the files now too?

Copy link
Member

@javiercn javiercn left a 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?

@HaoK
Copy link
Member Author

HaoK commented Dec 10, 2020

Ok I will update the PR to remove all the content as well now

@HaoK
Copy link
Member Author

HaoK commented Dec 10, 2020

Is anyone aware of any files/content that live outside of the project templates directory for these wasm templates? The build is green but...?

@captainsafia
Copy link
Member

@HaoK AFAIK, template files don't exist outside of the templates for Blazor.

@HaoK HaoK added the Servicing-consider Shiproom approval is required for the issue label Dec 14, 2020
@ghost
Copy link

ghost commented Dec 14, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants