FullName, Len Wscript. CreateObject "WindowsInstaller. OpenDatabase databasePath, openMode : CheckError ' Create an install session and execute actions in order to perform directory resolution installer. Commit : CheckError Wscript. Echo message Wscript. Quit 2 End Sub. Posted by: cygan 13 years ago. Posted by: sk 13 years ago. It could also be done creating a component with a dummy file empty text for example and set that file as keypath for the component.
Then add the other files to that component. If you have files that install in different directories you have to repeat this for each directory. A simple custom action that copies the file is also a possibility. Rating comments in this legacy AppDeploy message board thread won't reorder them, so that the conversation will remain readable.
Answer this question. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Collectives on Stack Overflow. Learn more. Asked 6 years, 2 months ago. Active 2 years, 11 months ago. Viewed 8k times. Thank you for your answers! Rami A. Geert van Gorp Geert van Gorp 51 1 1 silver badge 2 2 bronze badges. Add a comment. Active Oldest Votes. I wonder if you means ProductVersion instead of a FileVersion? Add a comment. Active Oldest Votes. I will add some links for you and a summary.
The use of companion files is what I would recommend. Hacking file versions I do myself sometimes - just to make things work. I prefer to move or rename files to "remove the problem".
See the above links for more on the above "options". I'm not sure this is an answer to my question. My requirements are quite simple. During the first msi installation there would be already files in the folders I'm installing to.
These files don't come from msi, they were manually copied earlier. I just want them to be overwritten. I don't care about their versions some of them are archaic dlls 10 years old, which versions? After the msi is installed upgrades will proceed in a "civilized" way, I do it already and see no pb with it.
The file overwriting rules are very complex with MSI. Please check that link to understand how they work. Thursday, September 10, PM. I performed a test on my side, but I cannot reproduce this issue on my side. How did you package these Dlls? Are these Dlls from a Merge module? If the Dlls is from a different, they are considered as diffirent Dlls, and will be installed without replacing the older ones usually they gets installed into WinSxS folder.
Based on my understanding, the upgrade mechanism for Visual Studio setup project and Visual Studio are different. In VS the older files is removed before new files get installed. However, in VS the uninstallation of the older files is at the end. And here is the file version rule for MSI.
0コメント