runtime error occurred during the loading...blah blah blah

[got2bmvp]

OK, so I have looked through this listserv. I have read Randy Byrne's
article. I have tried using a shim. I have contacted Microsoft (have
a nice weekend, they tell me...sheesh!). I cannot find the answer to
save my life.

I am getting the runtime error message when I try to load a .NET
add-in. I modeled my add-in after Randy's (thanks for that, Randy)
odc_oladdin. I can get the addin to run when I install it by right
clicking on the setup file in VB.NET and then pressing F5 to debug the
code...everything works fabulously that way.

The problem happens if I DON'T press F5 and just open Outlook. The
registry key turns from a 3 to a 2 and i get the load error. Funny
thing is that the same thing happens with Randy's original addin too...

Any help would be appreciated!

Mike

 

[Ken Slovak - [MVP - Outlook]]

Is your assembly (and Randy's) set to be trusted?

 

[got2bmvp]

Sure is. Everything on the second tab is wide open.

 

[Ken Slovak - [MVP - Outlook]]

No, I mean CAS security for the assembly.

 

[got2bmvp]

Not sure what you mean by CAS security.

No, I mean CAS security for the assembly.

 

[Guest]

I think that Ken means that you should convince yourself that the add-in has
been given proper permissions.

So start the .NET Framework 2.0 Configuration applet which incidentially is
*not* bundled with the 2.0 redist!
Get it by downloading the SDK.

Open My Computer|Runtime Security Policy|User|Code Groups|All_Code

You should now the add-in two levels below All_Code and see this

"Assemblies matching the membership condition are granted this permission
set at the current policy level: FullTrust.

Permission Set Description:
Allows full access to all resources"

Mind you, my add-in has been deployed to three PC's and it still doesn't
work on all three so something besides CAS is in play.

Regards
Peter

 

[michael]

Hi there, i got the same problem with a word add-in... did u use VSTO
for your outlook add-in?

 

[got2bmvp]

I'm actually using VS 2003 and Outlook 2002 (so no VSTO)