We received a lot of feedback from the community and other developers about the Extension Manager VSIX manifest and made some changes in Beta 2. Some of the changes included:
- Making the schema less strict so elements don’t need to be in a particular order
- Following XML standard casing
- Clearing up ambiguity about supported VS editions and products since the manifest works for isolated shell applications as well
- Adding support for per machine installations (remember, per user installs are still preferred and a better user experience for customers getting your extension)
- Adding version info for the VSIX manifest
- and lots of little changes to make things easier and better.
Ofcourse, these changes will require you to update your Beta 1 manifest files. Instead of manually tweaking your XML, we’ve built a nifty cool VSIX Manifest Converter tool to help you move your Beta 1 manifest to Beta 2.
The tool is attached to this blog post. To use it, just run the exe in the directory where your VSIX or extension.vsixmanifest file is. The tool will automatically convert the manifest. If you have a VSIX, it’ll crack open the VSIX, update the manifest and repackage your VSIX.