Setup your VS debugging environment for a COM add-in (Excel 2003)

  • Thread starter Joannes Vermorel
  • Start date
J

Joannes Vermorel

I am currently working on a COM add-in for Excel 2003 under Visual
Studio 2005. The logic is written in C# using interop. For now, all
the add-in registration is handled directly a WiX script that
generates the MSI package.

For now, when I want to test the addin, I run the MsBuild script that
generates the MSI, install the add-in and test.

Yet, this approach is very cumbersome, plus I can't using the Visual
Studio debugger.

Does anyone knows how to setup an "VS environment" that would let me
test the add-in by simply hitting F5 under Visual Studio?

Thanks in advance,
Joannès
http://www.lokad.com sales forecasting
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Add-in does not load 0
How to diagnose a COM addin that fails to load? 0
tlbimp vs. primary in VS project file 0
Referencing .NET DLL built for COM in VBA 0
Using VSTO2003:Excel 2003 appears and then disappears immediatelywhen debugging with VS 0
Error messages received when COM Add-in is load in Excel 0
COM Add-in deployment 4
Office COM Add-in Deployment 0

Top