On 12/05/2014 04:51 AM, Nicolás Alvarez wrote: > 2014-12-04 4:26 GMT-03:00 Valery Portnyagin <valery.portnya...@oracle.com>: >> On 12/02/2014 10:15 PM, Phil Wilson wrote: >>> If you're saying that two MSI products are incompatible and you want >>> to make sure that a product cannot be installed if another one is >>> already installed then some choices are: >>> >>> You use Upgrade and UpgradeVersion elements with OnlyDetect="yes" that >>> target the specific incompatible installed product. The upgrade logic >>> will look for that product and set the property associated with the >>> upgrade. This subject to the rule that both products are per machine >>> (or both per user). If that property is set you could trigger a dialog >>> box. >>> >>> If there is a file with a specific version associated with the >>> incompatible product you could do a File Search for that specific >>> version. Again, a property will be set if the file is found. >>> >>> These, and your request, have the problem that in a silent install >>> there is no UI so do you want to go ahead with the install or not? If >>> you choose not to do the install at all if invoked silently then it's >>> better to do that with a launch condition, and WiX generates MSI files >>> with FindRelatedProducts before launch condition checks, so you could >>> use the upgrade property in a launch condition. >>> --------------- >>> Phil Wilson >>> >> Hello Phil, >> Thank for the answer. >> but I say about other case. >> there is one package A (msi package) and there is package B (also msi >> package). >> they are combined inside one exe bundle C. >> User install product C. >> Next step, user gets a new version of package B (just download from >> vendor site, for example). >> And try to install it. >> But for some reasons package A depends from particular version of package B. >> So, it is pleased if user will see some message with warning like "other >> products are installed which depend on that product". >> and he may decide to do or not to do this upgrade. >> >> And how i think, such logic can be realized via Requires/Provides >> Elements from Dependency Extension. >> But there is lack of information about this option/feature. >> >> Anyway, if there is another approach to achieve this i will appreciate >> for any clues or explanations. > I'm quite sure the logic to display such a message would have to be in > the new version of package B. So if B is coming from an external > vendor, I don't think you can do what you want... >
From Requires Element (Dependency Extension) description: This element declares a dependency on any product that uses the Provides element. If that product is uninstalled before a product that requires it, the uninstall will err or warn the user that other products are installed which depend on that product. Upgrade logic consists two steps - uninstall old, then install a new package. So when i install a new version of package B i can expect "the uninstall will err or warn the user that other products are installed which depend on that product". This is what i want to see. What else, I have made different experiments with Requires/Provides elements, but i didn't find the right way to get a working WiX script. I am experimenting with 3 simple projects: 1. MSI A 2. MSI B 3. Exe bundle C (MSI A + MSI B) It doesn't matter where i put these elements, every time i see the same results. I see that in the registry under "HKCR\Installer\Dependencies" are created the same structure from key/records - Both MSI A and MSI B depends from bundle C only. How can i achieve the result when under "HKCR\Installer\Dependencies" i will see dependency of package A from particular version of package B? regards, Valery. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
