Got error message figured, but Add-in still won't show
Hi Ken
Thanks very much for taking the time for helping me out with this.
My Add-In isn't showing up in the Disabled Items box. It is, however,
changing it's LoadBehavior entry in the registry from 3 to 2. I notice on
client computers now a message that actually does report that it is failing
to load. Is there any easy way to figure out why? (I'm using the
IDTExtensibility2 method rather than VSTO).
There is a file in the VS.NET generated Setup files for my project that I
have marked "excluded", because it was giving me an error on setup. I can't,
however, figure out how to get it off the dependency list! I don't know what
part of the code needs it. However, when I choose to "open" it with the
resource viewer and look at the resulting hex, I see the name "stdole2.tlb"
in there. My IDTExtensibility code also uses the line "Imports
Extensibility", the two culprits you mentioned.
Do I need to somehow include those two files in the Setup project so my
users will get them?
When it comes to security policies, I'm afraid I don't know a thing. I
heard there is a .NET Configuration Applet from the SDK that you could use in
version 2.0 of the framework to edit security policys for code. Do I
understand right that if I use it, I can somehow change the level of trust my
Add-In is granted on other user's machines?
I'm writing for Outlook 11 (2003) and XP, which I have both of on my dev
machine. As I said, I'm not using VSTO. I am deploying just what VS.NET
plopped into my setup project for me. In my "setup" project's "Detected
Dependencies" folder is:
Version 2.0.50727 of the .NET framework, even though my machine has 3.0
installed (not sure why VS.NET isn't using 3.0, unless it's because I started
the project when it was version 2),
Interop.OUTLOOKADDINLib.dll,
Interop.Redemption.dll,
Microsoft.Office.Interop.Outlook.dll,
Microsoft.Vbe.Interop.dll,
office.dll,
olkaddin.dll,
and Redemtion.dll.
I am not using a shim (it's a new concept to me). I also do remember
installing the office PIAs, although I'm afraid I'm going to have to claim
ignorance here, as I'm still not 100% clear as to what they do for me...I
installed them because of a compiler error that I eventually figured out they
would resolved.
Thanks again for the help!
-Josh
|