Don Benson wrote:
> File/@Source="$(var.ClientInstall.TargetPath)"
>
> This worked great until I started to add the UI elements. I wanted to
> localize the UI, so I added localization files (wxl) for the different
> cultures we need. This broke the server compile. The localized clients are
> genera
DaveCory wrote:
> C:\Wix\light.exe -out BHARTI_DASH_A.01.00.1.msi
> CustomActions.wixobj DirectoryDefinitions.wixobj IconDefinitions.wixobj
> NewDi
> rectories.wixobj DashComponents.wixobj ServerConfig.wixobj
> ServerExecutables.wixobj ServerFeatures.wixobj boFiles.wixobj
> Ser
Hi there,
Apologies if this is really simple but not sure what I've done wrong. I'm
using the Wix Tutorial to try and build my own custom UI, however, before I
add any custom dialogs I'm trying to simply create a custom GUI and build
against that.
The steps I've done is as follows
1) Copy WixUI
How do you detect Server 2008 Core?
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovati
On Sat, Mar 7, 2009 at 8:40 AM, Bob Arnson wrote:
> Bob Arnson wrote:
>> So that's the literal interpretation of the MSI SDK: You can only
>> schedule RemoveExistingProducts before InstallFinalize if it follows
>> InstallExecute[Again]. Not sure what to do about it at the moment...
>>
>
> I added
Bob Arnson wrote:
> So that's the literal interpretation of the MSI SDK: You can only
> schedule RemoveExistingProducts before InstallFinalize if it follows
> InstallExecute[Again]. Not sure what to do about it at the moment...
>
I added InstallExecute and InstallExecuteAgain standard actions
6 matches
Mail list logo