I'd be very interested in this as well. At the moment, when we release a new version of an application, we go to the GPO (Windows 2000 Group Policy Object) that installs the application, uninstall it via the GPO, upload the new version to the server, then redeploy the application via the same GPO. It works, but if we forget to remove the old version via the GPO, we need to manually uninstall it from the workstations, which is no good.
I'm sure there is a way to do this with versioning. Any suggestions? Thanks, Erick > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Bill Bassler > Sent: Wednesday, April 28, 2004 9:54 AM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] Versioning guidelines for Windows Installer > > Can anyone point me to version guidelines for .Net solutions > and a related Windows Installer projects? > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > Some .NET courses you may be interested in: > > NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles > http://www.develop.com/courses/gaspdotnetls > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
