[release/6.0-rc1] Update RazorPage template to be able to be SxS with previous version#35731
Merged
dougbu merged 4 commits intorelease/6.0-rc1from Aug 26, 2021
Merged
Conversation
…rsions. - Update Web.ItemTemplates to use a versioned package identity - Bump up the precedence - Make unique identities - Add Framework symbol for RazorPage template
Member
pranavkm
approved these changes
Aug 25, 2021
|
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. |
Contributor
|
@dotnet/aspnet-build this is approved. Could you merge this? |
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #34598 to release/6.0-rc1
/cc @javiercn @phenning
Customer Impact
6.0 templates are not preferred when 5.0 templates are installed. @phenning can you confirm?
Testing
@phenning I assume you did manual testing.
Risk
I would say low, but I'll let @phenning speak for it.