I have a VSPackage with a custom editor. I want it to show up in the solution explorer with a custom icon, which will require a custom deployment step.
Here are my deployment requirements:
- As explained here, allow users to easily update to new versions of my extension using the Visual Studio Gallery (In VS Tools > "Extensions and Updates" > Updates).
- As explaned here, I need to run a custom installation step to set up the custom icon in the registry (outside the VS registry hive, which means PKGDEF files can't do it).
As explained here and here, instead of using a VSIX file, I could create a custom installer that places the extension files directly in the user/machine-wide extension folder on the target machine.
Problem is I think the easy extension update process from the VS Gallery would not work. Can I get both of the requirements above? If so, how?
As a workaround, could I check if the icon is set up correctly in the package Initialize method, and if not, run some custom code to set up the registry settings? In this case I can stick with VSIX deployment and the auto-updates work.
Alternatively, if I create a custom installer that deals with updates and copies new versions of the extension files to the extension folder, how do I register it so that VS "Extensions and Updates" checks the VS Gallery version number for updates?