-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Update precedence and Identity of templates for 5.0 #19248
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
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.
Thanks!
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. |
@ryanbrandenburg doesn't downstream packaging use the template names i.e. doesn't something else need to change to pick up the new "5.0" templates? |
Are we taking this today, or will we have to wait for Monday? CC @mmitche as this will effect the timeline for preview1 |
Without this change, if 5.0 preview1 is installed, users wont be able to create 3.1 projects in VS. |
@dougbu packaging is dependent on the package authoring not the individual template identities. I believe the package is currently being created properly. |
Tactics approved this, merging |
Co-authored-by: Ryan Brandenburg <[email protected]>
Fixes #17553.
@mkArtakMSFT I believe it was you who created the mapping for
https://aka.ms/aspnetcore/5.0-third-party-notices last
time? We need to do that again. This is basically a copy of https://github.com/dotnet/aspnetcore/pull/14637/files, plus the fact that we have a new template.