fix(msix): Adjust project creation ordering #5161
Merged
Conversation
This file contains 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
|
|
carldebilly
approved these changes
Feb 5, 2021
|
The build 24481 found UI Test snapshots differences: Details
|
|
The build 24481 found UI Test snapshots differences: Details
|
|
The build 24481 found UI Test snapshots differences: Details
|
|
The build 24481 found UI Test snapshots differences: Details
|
|
The build 24481 found UI Test snapshots differences: Details
|
davidjohnoliver
approved these changes
Feb 6, 2021
|
The build 24481 found UI Test snapshots differences: Details
|
|
/azp run |
jeromelaban
added
the
ready-to-merge
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The build 24541 found UI Test snapshots differences: Details
|
|
The build 24541 found UI Test snapshots differences: Details
|
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
GitHub Issue (If applicable): fixes #5151
PR Type
What kind of change does this PR introduce?
What is the new behavior?
Applies workaround suggested in https://developercommunity2.visualstudio.com/t/legacy-projects-are-not-present-in-the-xaml-editor/1324898
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Internal Issue (If applicable):