Re: [WiX-users] How to keep guids in similar setups

. Best regards, Ilya Slobodin Blair wrote on Thu, 02 Dec 2010 13:50:04 -0800 > Do those components actually share anything (registry keys, COM > registration, > custom actions, whatever) that require them to have the same guid? > > Original Message > Subject: R

Re: [WiX-users] How to keep guids in similar setups

update Program Files\Product 1\A.dll because it is considered to have the same version. Is there a way to solve this problem on Vista and 7 other than making .wxi files with different GUIDs for each configuration. Best regards, Ilya Slobodin Original Message Subject: Re

Re: [WiX-users] Patch creation problems

, action state of all components becomes "Local" but no action is really executed on the components not included in the patch. When REINSTALL=ALL REINSTALLMODE=omus are not set, action states of the files being patched are set to "Local" by the msi engine. Best regards, Il

[WiX-users] How to distinguish between "full repair" and "self-repair"?

veSource when a new user starts our product for the first time. Best regards, Ilya Slobodin - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications

Re: [WiX-users] Localization filename change

until I need the new functions in that build. What's why I call this a break of compatibility. Best regards, Ilya Slobodin - Original Message - From: "Neil Enns" <[EMAIL PROTECTED]> To: "General discussion for Windows Installer XML toolset." Sent

Re: [WiX-users] Localization filename change

) where CultureSuffix is overridable and is empty by default when single culture is used? Or, even better, put $(TargetDir)\$(CultureSuffix)\$(TargetName)$(TargetExt) into the overridable property, say TargetDirLocalized. Best regards, Ilya Slobodin - Original Message - From: "

Re: [WiX-users] Localization filename change

are usual for a growing project. Best regards, Ilya Slobodin - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great p

Re: [WiX-users] Localization filename change

g was closed with the following reason: Bob Arnson: That was an intentional change to support building multiple localized outputs from a single project. Best regards, Ilya Slobodin - This SF.Net email is sponsored by the Mobl

Re: [WiX-users] SqlScript, XmlFile, Pyro and patching

otidy argument. Very helpful to see what tables are included in the patch and what are not. Best regards, Ilya Slobodin - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linu

Re: [WiX-users] Patch install: MoveFiles and component action states

, that is a patch is being installed, REINSTALL & REINSTALLMODE must not be set. If set, action states of all components are set to "Local" but no real action on these components is taken. But, MoveFile reco

Re: [WiX-users] Patch install: MoveFiles and component action states

(as expected) 2. msiexec /update Patch\Patch.msp REINSTALL=ALL REINSTALLMODE=omus /lv* Logs\PatchBad.log File Sample.txt is patched SampleDb.txt is renamed to SampleDb.bak while the original file SampleDb.txt is not reinstalled (confusing) Best regards, Ilya Slobo

Re: [WiX-users] Patch install: MoveFiles and component action states

not be executed. But it IS executed if required arguments REINSTALL=ALL, REINSTALLMODE=omus are set. Best regards, Ilya Slobodin - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that

Re: [WiX-users] Patch install: MoveFiles and component action states

y in the MoveFile table means that file is moved when referred component is reinstalled (the file from source is copied to the real file on disk) and not moved when file is not reinstalled. Best regards, Ilya Slob

Re: [WiX-users] Patch install: MoveFiles and component action states

This makes MoveFile table completely non-functional when the file being moved is not included in the patch. In our case it's a database, much bigger than the code itself. So, the only solution is to avoid MoveFiles and write CA to suppoft custom MoveFileEx? Best regards, Ilya Slo

Re: [WiX-users] Patch install: MoveFiles and component action states

Sorry for the mistake in the explanation. The problem does not depend on UI, it depends only on REINSTALL & REINSTALLMODE I have to use the following command line to get my update installed: msiexec /passive /update Patch.msp REINSTALL=ALL REINSTALLMODE=omus Best regards, Ilya Slob

Re: [WiX-users] Patch install: MoveFiles and component action states

Patch.msp But, if we have UI, msiexec /update Patch.msp /passive does nothing. If I add REINSTALL & REINSTALLMODE my database is gone. Any ideas how to avoid REINSTALL & REINSTALLMODE and install the patch? Best regards, Ilya

[WiX-users] Patch install: MoveFiles and component action states

ently I temporarily solved the problem by modyfing with the patch MoveFiles condition to "NOT PATCH". Is there a better solution? Best regards, Ilya Slobodin - Sponsored by: SourceForge.net Community Choice A

[WiX-users] How to keep guids in similar setups

Product Base 3. Uninstall Base (StartMenu\Programs\My Product Base\My Product Shortcut.lnk remains and it has Action: Null in the log) 4. Uninstall Pro (Pro\Shortcut to My.exe uninstalled) I use MSI 3.01 Could someone comment on this? Best regards