[WiX-users] pseudo-loc UI shows {WixUI_Font_Bigger} & {WixUI_Font_Title}

2009-09-19 Thread Lian Jiang
Hi, Our pseudo-localized installer shows {WixUI_Font_Bigger} & {WixUI_Font_Title} on all install windows. We just reused Wix's dialogs and localized the Wix strings. The same behavior was observed in one of our previous project's installer. How can we fix this issue? Appreciate your help!

Re: [WiX-users] Major Upgrade install - why are files missing?

2009-09-19 Thread Scott Palmer
"The Component Rules" seem to be nearly impossible to follow. Assuming I understand them (a significant assumption), the only way to follow them that I can see is to not allow users to choose an install folder (since the rules say that every component must only install to one specific path

Re: [WiX-users] Major Upgrade install - why are files missing?

2009-09-19 Thread Blair
If you are using the C/C++ runtime MSM modules, you must place the RemoveExistingProducts action either right before or right after InstallFinalize (if you put it right before, it must be (immediately) preceded by an InstallExecute or InstallExecuteAgain action). See http://msdn.microsoft.com/libra

Re: [WiX-users] Major Upgrade install - why are files missing?

2009-09-19 Thread Scott Palmer
There is a single custom action to run a command line after the files required are installed. This command appears to work fine in the case where I am not uninstalling a previous product, though it doesn't matter much if it doesn't run. The common component I'm installing is a company-pri

Re: [WiX-users] Upgrade Detection (FindRelatedProducts) with EmbeddedUI

2009-09-19 Thread Konstantin Vlasenko
Open your msi via ORCA.exe. Find the ordering of the custom actions. Set desired order for FindRelatedProducts. 2009/9/19 AG Crum > Has anyone done an upgrade while using an EmbeddedUI? I asked a similar > question a while back and was wondering if anyone has figured out a way run > the action F