Hi Mike, If I understand your question, I think what you need to do is set the the instance of Visual Studio containing your Add-in so it starts another copy of Visual Studio when it runs. I kind man called Sam Gentil gave me this answer. It's in the archives on 26 March this year if you want to look it up. To save you the trouble, here's the text:
>Setup inside the project the Configuration Property - >Debug - Start Application to be devenv.exe (VS.NET). Then when you step and >debug, it will launch another instance of VS.NET stepping through your >addin. The slightly confusing thing is that all this does is start up a new instance of Visual Studio. After that (Assuming you used the Create Add-in wizard) you have to create or load a project and run your Add-in from the menu in this new instance. As soon as you do this you will be into your code in the other instance of Visual Studio. Add-Ins are supposed to be easier with VS.NET than they were with VB6 but just at the moment I find the object model is just bigger and more complicated, with multiple ways of doing everything, and the documentation is even more sparse. If you find you take to it like a duck to water plesae let me know, and I'll be asking you the questions! HTH Regards, Jay Ayliff Stalis Ltd You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
