Geek Answers Handbook

Allow .NET 2.0 to run executable files from the network with full trust

Guys it can't be real

I am trying to run an executable run of .NET 2.0 from a network drive, and it turns out that since Microsoft.net 2.0 does not have mscorcfg.msc installed on the 2003 server, I have to install the full SDK to get it. I just want to run a dang thing without downloading a 350Mb piece of shit!

Sorry for the disclosure ... Anyone might think of a simple solution?

EDIT1 . There seems to be a misunderstanding as to what I want to achieve. This is for my test environment. I have many virtual machines and all I want to do is just disable dang security. The task seems so trivial, but so far it seems to me that I need to deploy the SDK, or 3.5 SP1, or some other package with several terabytes for each machine to achieve this.

+6
security
source share
5 answers

You can configure security with caspol.exe without requiring msc. However, it would be easier to use the ClickOnce deployment (“publish”) from VS2005 - this avoids most security issues with network resources (but can be hosted on a network resource).

+2
source share

You can try running the following command from the .NET command line -

caspol -cg All_Code FullTrust

This gives the code group "All_Code" a full set of permissions.

+3
source share

You can try upgrading to .Net 3.5sp1 or later. This should be able to run .Net 2.0 code, but they changed the trust system in this version to fix this deployment scenario.

In addition, I do not have a link, you do not need a full SDK to get mscorcfg.msc. I saw that it is included in a much smaller package. But then again, I don't have a link, and you can do it as easy as I do.

+1
source share

Warning. Perhaps I do not understand your question, since I do not understand the link to mscorcfg.msc. Is .NET installed on the machine?

If so, a simple solution:

  • Configure security so that you can run the program from a network share

If not, a simple solution:

  • Install .NET Runtime

Sorry for the fact that this is a simple solution.

Other solutions include:

  • Packing your program into a .EXE file with the corresponding fragments of the .NET environment in it. This packaging requires specialized software, and it’s not cheap, although the exact names of these tools go away from me.
  • Rewrite the program to not use .NET
-one
source share

More articles:


All Articles