Describe the migration path from old VSIX to .NET CLI
nils-a opened this issue · comments
especially, https://devblogs.microsoft.com/dotnet/net-cli-templates-in-visual-studio/ states
Templates with CLI and Visual Studio installer (VSIX) manifests with different IDs will show duplicates. Changing to a single identity for the template is recommended.
My expectation when reading that was, that the .NET CLI templates would "hide" the old VSIX templates if I got the IDs right.
First question: Is that true?
And if so, which IDs should be synced? I tried setting $.identity in template.json to TemplateID from the VSIX .vstemplate but that's not it.
Sorry for the delay in responding here. If you have a VSIX which has a vstemplate, you can continue to use that if you like. vstemplate technology isn't going anywhere, and is still supported. Most templates in Visual Studio are built with the vstemplate technology.
If you want to switch to Template Engine (dotnet new) templates, I would recommend releasing a new update of the existing VSIX which contains the Template Engine template. For info on how to create a vsix with templates, I have some info at https://github.com/sayedihashimi/template-sample#how-to-ship-a-template-inside-of-a-visual-studio-extension-vsix.
Let me know if that answers your questions.
The point I really wanted to know was:
https://devblogs.microsoft.com/dotnet/net-cli-templates-in-visual-studio/ states
Templates with CLI and Visual Studio installer (VSIX) manifests with different IDs will show duplicates. Changing to a single identity for the template is recommended.
Which IDs should be placed where?
I tried setting $.identity in template.json to TemplateID from the VSIX .vstemplate but that's not it.
@phenning can you clarify this?
@phenning gentle ping