I recently got started with extension development by adding a new command to the project context menu that lets me run the current project without debugging it (and without actually having to set it as startup project); similar to what old VSCommands used to do.
Now I found another thing that might be useful to me, but when I created a new Command using the provided Template (Add > New Item..., Custom Command) it add 5 new files to the project: the Command itself, aPackage-derived class for registering the command, a VSCT file to provide the locations/resources/etc. and an image/icon for it.
This also leaves me with a second entry in the About menu since they seem to be separate packages.
Is this the way to go, or should I refrain from using Add > New Item for those things and instead simply copy the existing commands over, reusing the same VSCT and Package-class for all of them?
I've read something about best practises to create different VSIX packages altogether instead of packaging things into one (like VSCommands or Power Tools), but this seems a little unwieldy for my purposes (where I'd want to drop in a package and get my 2...3...4
commands that make my own life easier, regardless of what various best practises say).
Thanks for reading,
- BhaaL