I\'m creating a custom test runner for my project. So I\'ve created a test vsix project which can be registered in Visual Studio.
I also knows that I load the extens
I've built a few Visual Studio extension and I've never found a good way to debug a VSIX. You can launch an experimental instance, but I've found this to be the slowest possibility.
This is the workflow I use:
devenv.exe
I've found this to be much faster than launching the VS Experimental Instance. But it's still quite arduous.
The other thing I highly recommend, is to abstract as much of the Visual Studio API as you can do unit testing and doing only the bare minimum of testing in Visual Studio. For example, in a project I'm working on now, pMixins, I've abstracted out the Visual Studio event system (VisualStudioEventProxy) so that my infrastructure doesn't have a hard dependency on the event api, and I can write a test which simulates events.