-
Notifications
You must be signed in to change notification settings - Fork 335
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
Fix two VSIX issues stemming from Reunion -> WindowsAppSDK rename #1192
Conversation
After the rename, it was decided to revert the VSIX id to the original name so as not to break upgradability and continuity. Unfortunately, the repositoryId elements in the individual templates weren't updated. Additionally, the original rename introduced a typo in the XmlPoke build target responsible for replacing the placeholder package versions with the actual package versions.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -77,7 +77,7 @@ | |||
<OriginalNugetRepositoryId>$(_tempVsTemplateNugetRepositoryId)</OriginalNugetRepositoryId> | |||
<!-- 'ExperimentalNugetRepositoryId' needs to match the value set by the XmlPoke query for | |||
"/ns:PackageManifest/ns:Metadata/ns:Identity/@Id" in Extension\WindowsAppSDK.Extension.csproj --> | |||
<ExperimentalNugetRepositoryId>$(_tempVsTemplateNugetRepositoryId).Experimental</ExperimentalNugetRepositoryId> | |||
<ExperimentalNugetRepositoryId>$(_tempVsTemplateNugetRepositoryId).Preview</ExperimentalNugetRepositoryId> |
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.
Does this make it so the name of the vsix file now has preview in it instead of experimental?
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.
I thought that VS used the VSIX Id, not the filename. I'm going to try testing it now.
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.
It needs to match the VSIX ID, as I noted in the comment. :)
…hub.com/microsoft/ProjectReunion into user/defaultryan/fix_vsix_rename_issues
Fixed the cases mentioned by alwu. |
@DefaultRyan Please cherry-pick fe787c7 (fe787c7) for the change that removes the Single-project MSIX Packaging project templates. |
we want this change in main and experimental. But your change may only for experimental. In reply to: 894549399 |
…s from the experimental VSIX (cherry picked from commit fe787c7)
If it's broken, it's broken. In this case, I don't see much, if any benefit to isolating this change only to the experimental release branch. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…eholder as the 'default' version in our source .vstemplate files
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
After the rename, it was decided to revert the VSIX id to the original
name so as not to break upgradability and continuity. Unfortunately,
the repositoryId elements in the individual templates weren't updated.
Additionally, the original rename introduced a typo in the XmlPoke build
target responsible for replacing the placeholder package versions with
the actual package versions.