Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There is a .Net executable (with a group of DLL’s etc) that up to 100 people will be using simulatiously during the course of the day. Is it still acceptable/good practice to have all the users just have a shortcut to the network path for this executable? Or would it be better to copy the .exe, .dll’s, etc locally to each users machine? What are the pros/cons of each and is there a standard way of doing this type of thing?
Having multiple people running the same application via a network share isn’t a great idea. Of course, deploying a stand-alone application to 100 users is a maintenance nightmare. Imagine that you need to deploy a new feature. You (or some other poor sucker) is going to have to go around to each PC and update it.
I’d recommend making a ClickOnce installer for the application. That way, you could provide your end-users with a link to the installer, and the application can automatically update itself as necessary.