How to run a DotNet Framework 2.0 Application from a Network Share
Kimmo | February 3, 2010Running a DotNet Framework 2.0 from a network share or an UNC path just plain doesn’t work. You get an error message such as the the one to the right.
I pretty much never thought much of it, because in some mysterious way I never encountered a situation where this might be an actual problem. Well. A couple a weeks ago a customer hit into this problem, and for a reason or another they really needed to run their application (not admodify.net!) from a network share.
Here’s a couple of links on the issue and remedy:
http://support.microsoft.com/kb/320268
http://msdn.microsoft.com/en-us/library/a0ke3k86(VS.71).aspx
However, for the brave one, here’s an example wildcard solution. Run it from a CMD prompt from within C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
caspol -m -ag 1 -url "file://\\*" FullTrust -exclusive on
Did you know that Citrix was originally supposed to be Citrus? Well, the name was already taken but that didn’t hinder them from, eventually, turning into sour. Anyhow that’s not the topic here. Broken WMI is, and that overlay product on top of TS/RDS commonly referred to as Citrix.



