VS.Net Setup Deployment Project
-
Not sure if this is theright forum but.... Does anybody know how to turn off the feature in a visual studio .net setup and deployment project that when you change an installed file it asks you to re-install the whole app. It is really annoying when you need to swap out a dll, ocx or exe on client site because you need to..(I know you shouldn't have to but this is a rushed job for a very large client) and then it insists on re-install replacing the dll, ocx, exe with the original....aaaahhhhhhhhhhhhhhhhhhhhh!!!!!!! Thanks for any help on this... Cheers
-
Not sure if this is theright forum but.... Does anybody know how to turn off the feature in a visual studio .net setup and deployment project that when you change an installed file it asks you to re-install the whole app. It is really annoying when you need to swap out a dll, ocx or exe on client site because you need to..(I know you shouldn't have to but this is a rushed job for a very large client) and then it insists on re-install replacing the dll, ocx, exe with the original....aaaahhhhhhhhhhhhhhhhhhhhh!!!!!!! Thanks for any help on this... Cheers
(I also answered this in the VB.NET forum) This is a built-in function in the Windows Installer service. There is not much you can do about this once the setup has been run. What happens is changing the file causes the Windows Installer to automatically put itself into Repair mode. You have a couple of options: 1) Reissue the entire setup with the new files, have the user uninstall the original application completely, then install the updated version. This is easy enough for you to do, but your client may not be very happy about it. 2) Author a Patch project. A patch project does several things. First it replaces any files that you need to replace. Second. it finds the original installation MSI and applies changes to the MSI so that it now recognizes the updated files as being the correct ones so Repair mode is no longer automatically in initiated because the versions have changed. Creating a Patch is way outside the scope of what you can do with the VS.NET Setup projects. You will need to download the Windows Installer SDK from Microsoft to even get started, and authoring MSI's is difficult and tedious. Good Luck! Robert
-
Not sure if this is theright forum but.... Does anybody know how to turn off the feature in a visual studio .net setup and deployment project that when you change an installed file it asks you to re-install the whole app. It is really annoying when you need to swap out a dll, ocx or exe on client site because you need to..(I know you shouldn't have to but this is a rushed job for a very large client) and then it insists on re-install replacing the dll, ocx, exe with the original....aaaahhhhhhhhhhhhhhhhhhhhh!!!!!!! Thanks for any help on this... Cheers
Unless you have added some new components, 3rd party assemblies, etc, you don't have to do a new install. You simply replace the .exe. But even if you have added some new components, most of the time you can simply copy those .dlls, etc to the users machine along with the new vb.net .exe. I have an update site on the web that is checked by my client's app each time they start it, If a new version is available, then it (and any other supporting files) are downloaded to the client's system and they are immediately updated without uninstalling and the installing the app.