A lot depends on what resources your app will be required to use. We went with a solution based on the application updater at www.windowsforms.net (which I don't see anymore - it might have been obsoleted by the application updater block). Our biggest enemy has been user permissions. We modified the code substantially for our purposes, and everything worked great, until it got into the production environment where not all users have the rights to modify and/or create files on their filesystems. This is especially prevalent in a Terminal Server environment for obvious reasons. No-touch deployment (NTD) handles a lot of these problems but the price is reduced access to resources for security purposes. Good luck.
________________________________ From: Unmoderated discussion of advanced .NET topics. on behalf of Andy Smith Sent: Wed 3/23/2005 8:15 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: [ADVANCED-DOTNET] Large-scale WinForms Client Deployments Does anyone have a recommendation on how to approach a large-scale (~2000 workstations) deployment of a Windows Forms application? I know 'One- Click' deployment is coming out with VS 2005 but I've got to get moving on it now. Does anyone have any experience with this and have some recommendations/tips etc? Are there any 3rd-party products that would help here? Any good forums that are a good reference for this? Thanks!! Andy =================================== This list is hosted by DevelopMentorŪ http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentorŪ http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
