B
br73
I am having what seems like a standard deployment issue with a VSTO add-in.
I'm hoping someone here can help point out where I'm going wrong. Basically,
I have a VSTO Excel 2003 add-in project that I have developed with Visual
Studio 2008. The add-in works successfully on my development machine but
fails on installations. The install systems have office 2003, .NET framework
3.5 SP 1, VSTO runtime 3.0 (I've tried with VSTO 2005 runtime as well - not
sure which is proper), the office 2003 PIA's and I have used CasPol to add
the install directory to the All_Code group with FullTrust. When I fire up
excel the menu item that is added by the add-in does not show up and the "COM
Add-in's" toolbox shows the following error for my add-in: "Not Loaded. A
runtime error occured during the loading of the COM add-in." I've researched
any dependency issues using fuslogvw tool to find that my add-in dll
successfully loaded. What I don't see in the fuslogvw tool is any of the
dependencies (e.g. Microsoft.Office.Interop.Excel.dll, etc.) being loaded,
successfully or unsucessfully. That about summarizes it. Any help is very
appreciated.
Bryan
I'm hoping someone here can help point out where I'm going wrong. Basically,
I have a VSTO Excel 2003 add-in project that I have developed with Visual
Studio 2008. The add-in works successfully on my development machine but
fails on installations. The install systems have office 2003, .NET framework
3.5 SP 1, VSTO runtime 3.0 (I've tried with VSTO 2005 runtime as well - not
sure which is proper), the office 2003 PIA's and I have used CasPol to add
the install directory to the All_Code group with FullTrust. When I fire up
excel the menu item that is added by the add-in does not show up and the "COM
Add-in's" toolbox shows the following error for my add-in: "Not Loaded. A
runtime error occured during the loading of the COM add-in." I've researched
any dependency issues using fuslogvw tool to find that my add-in dll
successfully loaded. What I don't see in the fuslogvw tool is any of the
dependencies (e.g. Microsoft.Office.Interop.Excel.dll, etc.) being loaded,
successfully or unsucessfully. That about summarizes it. Any help is very
appreciated.
Bryan