We have an application that is built with Excel as the front end using the Office object model. We were using a C++ shim to load it as a COM add in for Excel 2003, but I’ve updated it to use the latest VSTO for Excel 2007. I’ve also been using VS 2010 for the latest version. The problem is that everything works great on my dev machine in debugger mode as well as just launching Excel 2007, but I cannot get it to run on any other machine (my current target machine is Win7, development is XP). I’ve created a ClickOnce deployment of the Addin, and I can see it in the list of COM Addins, but when I check on it to load it nothing happens. I re-open the Addins manager and it is un-checked. I’ve also tried setting in in the registry, but as soon as I run it, it sets the registry back to do not load. I’ve tried everything I can think of and searched all over the web but no dice. Any help would be appreciated!
UPDATE: I was able to setup some VSTO Error notifications and I got this from my app as well as a basic Hello World app that I deployed with ClickOnce. I still haven’t found an answer, but I do know that this errors out before the add-in can even fire the Startup event:
Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateStartupObjectException:
Could not create an instance of startup object PrevisionAddIn.PrevisionAddIn in assembly PrevisionAddIn, Version=6.0.0.0, Culture=neutral, PublicKeyToken=null.
at
Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.ExecuteCustomization.CreateEntryPoint(String entryPointTypeName)
at
Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.ExecuteCustomization.Microsoft.VisualStudio.Tools.Office.Runtime.Interop.IExecuteCustomization2.LoadEntryPoints(IntPtr serviceProvider)
I figured out that the problem was with the version of VS 2010 that I was using. I built the project in the Beta 2 version, and hadn’t had time to upgrade. Once I did that, it worked as advertised. But I sure learned a boatload about how to get this thing up and running!
Thanks again!
-Erick