Hi Wizrr,
Thanks for the reply. I tried the following:
1. installed office2003-kb907417sfxcab-
2. installed lockbackRegKey.msi on the test machine.
3. installed extensibilityMSM.msi on the test machine.
4. I tried to regasm.exe to register the pia on the test machine
Nothing worked tho. do you know any way to debug this error?
Thanks!
Main Topics
Browse All Topics





by: wizrrPosted on 2007-12-05 at 00:51:36ID: 20409808
I have no cure for this, and have not worked with VSTO, but i worked with plugins writen my own without vsto. Did you tried to install VSTO on that mashine by your own hands? Maybe some of native VSTO dll is missed? Is your plugin setup have VSTO as prerequisite?
-ENU.exe", i don't remember where i downloaded that package, you must search it.
I know - plugins must be registered in registry, but when using VSTO there must be special things to do. VSTO must act like loader for your plugin and there must be registry-key value for it (vsto must register self as plugin, and then it must load your plugin regarding of vsto plugin registering rules).
Also. Maybe you can find *.pdb files of VSTO and debug Outlook to know what happened?
Also. When i worked on my own plugin i was stack with issue. .NET 2.0 assemblies can't be loaded from Office 2003 unless you install this "office2003-kb907417sfxcab
I hope this can help.