Re: Excel PIA & .NET Security

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi =?Utf-8?B?aGVsaXg=?=,

I've only ever encountered using these properties when creating a VSTO 2003
document. It may well be that you're able to invoke the loader with C++,
about that I wouldn't know. But...

When Visual Studio sets up a C# or VB.NET VSTO project, it also executes a
caspol on the development machine (locational security) to trust the DLL
(project solution). If that folder is moved, or the project deployed, the
security policy has to be created on the target machines. As with anything
NET, this can be based on any combination of location, digital signature and
strong name you like.

Assuming that you have to do everything "from hand", then you also need to
set a policy (locational) to trust the DLL during development/testing.

> I'm pretty new to PIA and have been experimenting with Excel's Primary
> Interop Assembly and MC++. I've created a work*** that links into my dll
> via the _AssemblyLocation0 and _AssemblyName0 properties. However, when I
> open the work***, I get an warning which looks something like this:
>
> "The currenct .NET security policy does not permit myApp to run on the
> folder E:\. Do not change the security policy in your computer. The .NET
> security policy is controlled by your administrator or teh developer who
> wrote the custom macros...."
>
> All the code was developed on the same machine under the same user, so I
> don't understand why it's not letting it run. Any comments would be
> gratefully received !!
>

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)

.

Quantcast