I have a set of build tools that generate code. These are all SingleFileGenerator tools at the moment and I have managed to get them to work fine when installing manually through editing the registry keys and they work fine when I run the VSIX project in the debugger. What I can't seem to get working is getting Visual Studio to create a working .VSIX package to install.
Code will all ship under an MIT license. But right now, display of the license is the only thing that works in the installer! Any idea what I might be doing wrong?
I have told the dev environment to sign all the components. When I launch the debugger in the VSIX project, the development debugger sees all the tools and they all work as they should. But what escapes me so far is getting the things to work after using the installer. I have tried installing, uninstalling, rebooting the machine. I have checked the build process and there are no errors being thrown.
The .VSIX file does seem rather small, is there any way to work out what is in it? There is a [Content_types].xml, is that needed still or could it be the cause of problems?
I started off using version 1 of the package manager and then moved to version 2. I am using VS 2015 Community Edition. The VSIX package installs without any error messages or complaints. There are no errors or warnings listed in any of the projects. I have tried installing the .VSIX from the Debug and the Release builds. Same thing.
Is it possible that I am not actually getting a .VSIX being built and am somehow running an empty one? Why doesn't the project produce just the final VSIX package rather than a directory filled with the components? Should I write a script to build the components into a .VSIX and sign it? Is there an actual worked example somewhere I could follow?