Geek asks and answers

Is this normal for multiple users running a .net application that is stored in the same network directory?

There is an executable .Net file (with a group of DLLs, etc.) that up to 100 people will use simulatiously during the day. Is it acceptable / good practice that all users have a shortcut to the network path for this executable? Or it would be better to copy the .exe, .dll, etc. files Locally on every user computer? What are the pros and cons of each of them and is there a standard way to do such things?

+3
source share
2 answers

Having multiple users working with the same application through a network resource is not a great idea. Of course, deploying a stand-alone application for 100 users is a maintenance nightmare. Imagine you need to deploy a new feature. You (or other poor suction cups) will have to go to each computer and update it.

I would recommend making the ClickOnce installer for the application. In this way, you can provide your end users with a link to the installer, and the application can automatically update itself as needed.

+1
source

I agree with DBM, ClickOnce is the best practice for this situation.

, .Net , . , ( .Net, , ), .exe , , . .

+1

More articles:


All Articles