Add-In does not work properly after converting to VS 2005

S

Sandesh

I have developed an Add-In for Word/Excel/Powerpoint in VS 2003. I have three
different projects for each of those Add-Ins. Now I converted the project to
VS 2005 using the conversion wizard. After converting, I am trying to use the
Add-In in a machine that has got only framework 2.0(without 1.1). The Add-In
works fine for Powerpoint. It doesn't work for Word/Excel. I'm using Office
2003. When I try to debug the application, the OnConnection event is not
firing for Word/Excel.

I wonder if there are any dependancies for the Add-Ins in VS 2005. Please
suggest me a solution.

Thanks,
--Sandesh
 
X

XL-Dennis

Hi Sandesh,

Hm, it sounds as a difficult situation and the only thing that comes to my
mind is that the add-in has been blacklisted by Word/Excel.

To check it use the following steps:
1. Open up Excel
2. Select Help and then 'About Microsoft Office Excel'
3. In the dialog select the button 'Disabled items'

I recently wrote an article about troubleshooting:
http://www.excelkb.com/article.aspx?id=10206&cNode=7T5V0N
 
S

Sandesh

Hi Dennis,

Thanks for your reply. I have checked the disabled items in both Word and
Excel. In both the cases, there are no disabled items available. Now I am
going to read the article mentioned and try if that helps me.

Thanks,
--Sandesh
 
S

Sandesh

Dennis,

I just dicovered a strange behavior of Visual Studio. I tried to create a
new shared Add_In project in VS 2005 and tried to run it. Even for that the
OnConnection event doesnt fire. I just wonder if there is a problem with
Visual Studio itself. If so, can you please suggest me a fix?

Thanks,
--Sandesh
 
X

XL-Dennis

Sandesh,

Sounds as the installation of VS.NET 2005 may be corrupted...

Unless some other can give you a better solution my approach would be to
uninstall and then install it again, especially since you recently installed
it over the 2003 version.
 
S

Sandesh

That does not seem to be the problem of installation being corrupted. I tried
to convert the project from VS 2003 to VS 2005 in two different machines. The
issue repeats for the msi files created on both the machines.

Thanks,
--Sandesh
 

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

Top