bobchauvin

I get a security error when I try to debug my VSTO SE/Outlook add-in from a mapped drive. If I move it to my c drive, it works.

The properties for the app are set to Trust Assembly Location=True.

The biggest issue is that I cannot have a centralized location for my code.

Any ideas




Re: Visual Studio Tools for Office Debugging VSTO SE/Outlook on mapped drive fails, works from the C drive.

X4U

Hello bob,

as I know you have to set the correct policy settings.

Normal the assemblies are in on your local drive to when you go into

control panel / management / .Net Framework 2.0 configuration / Configure Code Access Security Policy

In the treeview under User / Code_Groups / All-Code

you will see an entry VSTOProjects and for each addin a Unique ID

under the unique ID you will see an entry Debug

Select the Debug entry and click on Edit Code Group Properties

Open the Edit Membership Condition Tab and check the path in the Url field.

If here is a wrong value correct it and save this value.

Try again.

Maybe you have to use a full UNC Path here, not the mapped drive letter.

Sourcecode:

I would use SourceSafe or TeamFoundationServer to have a centralized place for the Sourcecode.

This will give you also the option to have some versioning.

Hope this helps,

greets, Helmut






Re: Visual Studio Tools for Office Debugging VSTO SE/Outlook on mapped drive fails, works from the C drive.

bobchauvin

Thanks Helmut.

I think I was just expecting the development environment for debugging to work without CAS settings. I applied my CAS policy and it works.

Thanks for the suggestions.