Shared addin in vs2005 acting weird and broken after installing vs2003

T

tqvist

I have developed a working word addIn in vs2005.

Then the need came up for me to do some work on an old .net1.1 project,
so I installed VS2003.

Now my addin stopped working. I can install it but it's not registered
at startup.

So I tried to add a new shared addIn project in my solution -- just to
debug it.
Now the strangest thing happens: when I try to build the setup project
for my new debug addIn I'm prompted to install features from Visual
Studio 2003! From within Visual Studio 2005?

I have tried to restore file associations in vs2005 but that didn't
help.

Clueless. That's what I am.

Are there any known problems with installation of vs2003 after vs2005?
 

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

shared addin deployment issues 0
Excel add in from VS2003 to VS2005 3
Shared AddIn won't load in english excel 1
Shared AddIn does not start in Excel anymore 4
Shared addin setup for word 0
Oulook Addin in C# / VS2003 Crashes before Getting to IDTExtensibility2 interface 1
Addin Setup project for outlook 2007 using Visual studio 2008 7
COM Addin in .Net 2.0 not loaded in Excel 2003 1

Top