Hi all,
The version 1 has two components A and B which has a single file in each (A and . The version 2 has a new component C which has A and B files. The major upgrade installs the version 2 and uninstall the version 1, it removes these two files A and B. I guess it's happened because now they belongs to the other component.
How can I prevent removing of these two files by the major upgrade?
Thanks a lot,
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Major upgrade removes files
Started by
Irina
, Nov 22 2002 21:29
5 replies to this topic
Posted 22 November 2002 - 21:29
Irina Shirinsky
Software Engineer, Heroix Corporation
http://www.heroix.com
Software Engineer, Heroix Corporation
http://www.heroix.com
Posted 25 November 2002 - 16:46
Irina,
Do you intend to update the files A and B by putting them both in C?
Have you removed the components A & B from your Version 2 package?
Are these files .exe's or version files?
Do you intend to update the files A and B by putting them both in C?
Have you removed the components A & B from your Version 2 package?
Are these files .exe's or version files?
Posted 25 November 2002 - 17:38
Hi Dave I,
There two files : crviewer.dll and craxdrt.dll. They are still the same as in the version 1.0.
Version 1.0:
Component - crviewer.dll
Files - crviewer.dll
Registration - Extract at Build
KeyPath - a file location
Component - craxdrt.dll
Files - craxdrt.dll
Registration - Extract at Build
KeyPath - a file location
Version 2.0:
Component - Crystal Files
Files - crviewer.dll, craxdrt.dll
Registration - Use Advanced Setting
These files were installed and registered by the Windows Installer in the version 1.0. For now in the version 2.0, I register these two files manually (by C code) only if a system has older version of these files. It is a reason why I combined them to the one component and didn't set a key path to the file location.
The version of these files is the same in 1.0 and 2.0.
I have removed old components from the package.
Please let me know if you would to have any other information.
Thanks a lot,
There two files : crviewer.dll and craxdrt.dll. They are still the same as in the version 1.0.
Version 1.0:
Component - crviewer.dll
Files - crviewer.dll
Registration - Extract at Build
KeyPath - a file location
Component - craxdrt.dll
Files - craxdrt.dll
Registration - Extract at Build
KeyPath - a file location
Version 2.0:
Component - Crystal Files
Files - crviewer.dll, craxdrt.dll
Registration - Use Advanced Setting
These files were installed and registered by the Windows Installer in the version 1.0. For now in the version 2.0, I register these two files manually (by C code) only if a system has older version of these files. It is a reason why I combined them to the one component and didn't set a key path to the file location.
The version of these files is the same in 1.0 and 2.0.
I have removed old components from the package.
Please let me know if you would to have any other information.
Thanks a lot,
Irina Shirinsky
Software Engineer, Heroix Corporation
http://www.heroix.com
Software Engineer, Heroix Corporation
http://www.heroix.com
Posted 27 November 2002 - 07:38
If you install those files into the same location in both versions, you are breaking one of the component rules. So at least you should make sure your RemoveExistingProducts action is in the sequence somewhere before InstallFiles.
Stefan Krüger
InstallSite.org twitter facebook
Posted 27 November 2002 - 13:30
Hi Stefan,
I know that I have broken components rules. The RemoveExistingProduct action is located after InstallFinalize. I though there is any way to change an old (existing on a machine).msi file or any registry keys (e.g. unregister old components with these files) so that Windows Installer does nothing this old components.
Thanks a lot,
I know that I have broken components rules. The RemoveExistingProduct action is located after InstallFinalize. I though there is any way to change an old (existing on a machine).msi file or any registry keys (e.g. unregister old components with these files) so that Windows Installer does nothing this old components.
Thanks a lot,
Irina Shirinsky
Software Engineer, Heroix Corporation
http://www.heroix.com
Software Engineer, Heroix Corporation
http://www.heroix.com
Posted 27 November 2002 - 14:58
In the Upgrade table you can specify which of the features of the old version should be removed.
If you don't add an entry in the Upgrade table the old version will not be removed at all.
If you don't add an entry in the Upgrade table the old version will not be removed at all.
Stefan Krüger
InstallSite.org twitter facebook