There are several issues and differences when you run an app on your local
machine and on a network share. The latter is placed on the "Intranet Zone"
and therefore has lower privileges than when you are on your machine
(Fulltrust permissions by default).
So if you want to develop and debug/test your code as if you where running
from your network share, take a look at this post:
http://weblogs.asp.net/hernandl/arch.../26/96800.aspx

At the same time, you should "prepare" your app to be able to run under a
restricted Zone and you might check out this post:
http://blogs.msdn.com/shawnfa/archiv.../20/57023.aspx


--
Hernan de Lahitte
Lagash Systems S.A.
http://weblogs.asp.net/hernandl


This posting is provided "AS IS" with no warranties, and confers no rights.

"Jesse" <jaufiero (AT) cascodev (DOT) com> wrote

I've also got a blog entry on modifying policy to allow something like this to work:

http://blogs.msdn.com/shawnfa/archiv.../20/57023.aspx

In this situation, I would recommend signing your application's assemblies with a key, and then trusting the public key (without the version) on each
client machine. This will allow you to deploy future applications, and upgrades to the existing application without modifying policy again.

-Shawn
http://blogs.msdn.com/shawnfa

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they
originated.
--------------------