What is the best (and easy way) to package all required dlls of a Word 2007 add in? I have a C# .Net project which has got a Word 2007 addin. In my dev machine, I am able to see that add in under Add-ins tab. But, when I install in user's machine, the Add-in tab does not have my add in. After I build the .Net project, I get .vsto file. The same is packaged in Basic MSI and getting copied in INSTALLDIR. But, the user has to install the .vsto file by double clicking it in their machine to get Word 2007 add-in.

Can some one shed light on how this can be automated in InstallShield 2009? Or let me know if I am doing something wrong to package Word 2007 .Net Add-in (VSTO).

0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity