Okay guys, here is one that has me scratching my head...
We have 2 development centres creating 2 different packages. We use the functionality of the 1 product in ours and the files are shipped to us via a merge module.
Now the merge module that is sent to us was recreated and all the component GUIDS were changed. When we now try and upgrade the new components are all set to not install (as expected because it looks like they were never installed in the 1st place).
Now without changing the Product Code, is there any way I can force the new components to be installed when upgrading to a later build? I am also loathe to create a new feature and assign the merge module to it.
Any other ideas?
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.
Same feature, new components
Started by
reflex
, Sep 17 2003 13:32
1 reply to this topic
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 18 September 2003 - 09:22
You cannot change component codes in a minor update, so you will need a major upgrade.
Stefan Krüger
InstallSite.org twitter facebook