>I have a VFP 9 application that calls a VB.net 2008 dll that I wrote. The assembly used to work, but my latest update now gives the "That assembly does not allow partially trusted callers" from Foxpro when I call it on my development machine. I have tried adding
>

>Assembly: Security.AllowPartiallyTrustedCallers()
>

> to assemblyinfo.vb but still get the error.
>
>Here's the rub: I deploy the application to my test machine (a tablet running Vista 64bit) and it runs fine. I just had to reregister the dll on the tablet and off we go. I've tried everything I can think of on my development machine and always get the trust issue.
>
>Any advice would be greatly appreciated.

From your PC, is this a local drive or a map drive to something else on your local environment?

I assume you have the same .NET Framework and both environments. Is your assembly strong named?

I have no done anything like that but found an alternative that might work. See about:

[assembly: System.Security.Permissions.PermissionSet(System.Security.Permissions.SecurityAction.RequestMinimum, Name="FullTrust")]