One way to do it is to add the following code to the assembly:

using System.Security;
using System.Security.Permissions;

[assembly:SecurityPermission(SecurityAction.RequestMinimum,
UnmanagedCode=true)]

This will cause it to fail at file load time instead of runtime and the
exception is at least more understandable to the user.

Another way to do it is something like this:

class klass
{
   public static void Main()
   {
       try
       {
// Do something simple that should never fail for any other reason
       }
       catch (SecurityException)
       {
// Warn user that they need to copy the file before using it
       }
       // Execute as usual.
   }
}

This has the advantage that you can catch the problem and provide a
message box or Console message or something like that to tell them why
they need to move the file to their computer before using it.

Hi Jim,

Thanks for your post.

In addtion to Nick Hertl's reply, there is an article talked about how to
handle unhandled exception in .Net, for your information:
"Unexpected Errors in Managed Applications"
http://msdn.microsoft.com/msdnmag/issues/04/06/NET/

Hope this helps

Best regards,
Jeffrey Tan
Microsoft Online Partner Support