Deploy a .NET Network on a Network

Question

I have a .NET 3.5 application that I want to install on a client server, and workstations run it directly from a network share. I read a little that it seems that it is not as simple as simply copying the application to a network resource, as I would for a native exe. Unfortunately, it seems that there is no documentation on the correct / best way to do this (via ClickOnce or otherwise).

So how will I use this type of deployment? Am I just copying assemblies? Is there something with ClickOnce that can make my life easier and future updates easier? (Keep in mind, each client will have a different installation point on its local server.)

What I know so far:

Obviously, the .NET platform must be installed on every workstation; I think installing it using Group Policy is the way here.

I also read a little about using a network resource that requires full trust, but then I read that this is not a problem in version 3.5. Does anyone know the final answer here?

Answer 1

Starting with 3.5 SP1, you no longer need to run applications from a network resource. By default, they will work with full trust.

Vance Post: 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

I believe the actual change is in CLR 2.0 SP2, which you get with 3.5 SP1, but I did not find any specific documentation on this.

Answer 2

You can also use ClickOnce deployment so that ordinary users with limited rights can install the application locally. This deployment still lets you publish updates to your network share, and users automatically grab them. And it will work if you are stuck with .Net version up to 3.5sp1.

He also poses some other problems. For example, if you need to deploy an update and the user currently has an application running on the local computer, the file system may lock the file that you need to modify. ClickOnce skips this.