title: CAS: Running exe from intranet
body: <p>Before I get flamed and down-voted without mercy, my company will not allow the install of .NET3.5 on non-dev machines yet (others are currently on 3.0).</p>
  
  <p>I have a managed exe on network share that needs to be able to run from there.  This is a common problem with pre-.NET3.5SP1, but I cannot figure out how to solve it.  I have read  <a href="https://stackoverflow.com/questions/197835/how-to-get-rid-of-security-exception">this question</a>, as well as, <a href="http://blogs.msdn.com/vancem/archive/2008/08/13/net-framework-3-5-sp1-allows-managed-code-to-be-launched-from-a-network-share.aspx" rel="nofollow noreferrer">this article</a>, in addition to the MSDN CAS articles (which is like trying to read and understand a EULA).  I cannot seem to solve this problem.  </p>
  
  <p>I've tried signing it; along with other suggestions found in the articles.  The only way I've found to get it to run from the network is to make it a click-once application and publish it; which is unacceptable because it creates a bunch of different files in the published directory (which confuses our less-than-technical users) and creates entries in the Add/Remove Programs in the Control Panel.</p>
  
  <p>I'm just a dev, so I don't have rights to set/alter machine policies and such.  Can anyone give me step-by-step instructions (or point me to a easy-to-read site) on what needs to be done to enable this thing to run from the network?  Is it even possible without setting machine/domain security/software policies (which I don't have access to)?</p>
  
  <p><b>Edit</b><br>
  Ok... I expected to get voted down; however, it would be really nice if people would explain why they down-voted.  This is a serious question that many people seem to be having a problem with; and almost no one seems to know how to fix.</p>