[WiX-users] 答复: in wix bootstrapper theme file , how to use hexstyle to apply an imagefile?

Have you filled the ThemeFile Attribute with your theme file? Maybe you should post more source code, then someone may findout why it doesn’t work. -邮件原件- 发件人: 姚�� [mailto:zhao@utek-china.com] 发送时间: 2013年11月5日 14:07 收件人: wix-users@lists.sourceforge.net 主题: [WiX-users]

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

Hello, I have tested now with the DIFxApp.dll and DIFxAppA.dll (that also the DifxAppExtension is using), same result! When the USB device is connect and the driver is installed a second burn window is opening. It seems the only way to prevent this is a modification in burn ... Ulrich -- View

[WiX-users] Burn Bootstrapper - do multiple instance installs work

Can I do multiple installs with a Burn Bootstrapper, we need to install the version of an application with a different build number. I know this was not supported before please see - http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-and-MultiInstance-installs-td7581181.html J

Re: [WiX-users] Having issues with permanently installed assemblies and Major Upgrades

If you've got the older assemblies marked permanent, then I'm guessing that they are not in the newer major upgrade install. So the old product is upgraded and removed but the assemblies stay behind, right? The alternative would be to continue to ship the old and new assemblies for both old and new

Re: [WiX-users] Burn - Extracting packages in managed bootstrapper

use the -layout option for burn (should consider to add a custom action inside each msi to prevent running it without setup.exe) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Extracting-packages-in-managed-bootstrapper-tp7590268p7590293.ht

[WiX-users] Managed Custom Action which call win 32 dll,possible?

Hi, Is it possible to use MakeSfxCA.exe to add a window 32 dll called by the managed custom action? Thanks in advance -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Custom-Action-which-call-win-32-dll-possible-tp7590295.html Sent from t

[WiX-users] Modifying a stock WixUI sequence clarification...

I'd like to use WixUI_Minimal, but I need to insert one dialog and remove the EULA dialog. According to the last section of online docs found here ( http://wixtoolset.org/documentation/manual/v3/wixui/wixui_customizations.html), I need to copy WixUI_Minimal.wxs from the Wix source into my project

Re: [WiX-users] Having issues with permanently installed assemblies and Major Upgrades

Okay thanks for all your help/suggestions, but have found what the actual issue was. The MsiProvideAssembly returning: 1607 on 2 assemblies was actually the hint. After testing a few times I got it to the point where 2 assemblies were gone after the upgrade and they were the ones listed in the Msi

Re: [WiX-users] Modifying a stock WixUI sequence clarification...

In general, yes. -- John Merryweather Cooper Build & Install Engineer -- ESA Jack Henry & Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony [mailto:yellowjacketl...@gmail.com] Sent: Tuesd

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Classification: Public No you don't need to physically copy the wxs file, you just need to copy the You can substitute your dialog for the LicenseAgreementDlg dialog... i.e. 1

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Thanks that's what I thought... Here's what I've done... I copied WixUI_Minimal.wxs into my project and renamed it to WixUI_Minimal_Modified.wxs. Then I changed the UI's Id attribute to read... In my Product.wxs I added... If I build I get a bunch of errors about missing dialogs (ErrorDlg,

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

Hi again everyone, I have tried to do a WinDbg session tonight to single-step through the burn-engine to find out where the problem is. But I must confess that I lost track somewhere in the creation of sub-processes and communication via pipes :-( One peculiar thing came up though. I had "sho

[WiX-users] platform x86 vs AnyCPU problems

I have a Visual Studio 2012 Forms Application with 2 WiX installers - TEST and PROD. Because of a 3rd party dll, I need to restrict the output to x86 for all machines. My development machine is x64. In order to achieve this, - all Build configurations in the solution have the Forms application s

Re: [WiX-users] Change Wix UI strings at run time

Hi, I want to change the Wix UI strings at run time based on language selection in the Wix UI (in setup.msi file). Could anyone please help me on this? Thanks in Advance On Thu, Oct 31, 2013 at 9:02 PM, Phill Hogland wrote: > The CHM, the Wix tutorial, and searching this list, cover this s

Re: [WiX-users] Managed Custom Action which call win 32 dll, possible?

Just add it to the MakeSfxCA.exe commandline. It will be packaged into the *.CA.dll file and extracted with the managed assembly at "runtime". If building from a *proj file using the wix.ca.targets file, you can use the CustomActionContents property to add files to your CA's payload. > Date:

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Search your entire installer source code and make sure there isn't another pointing to "WixUI_Minimal" lurking around in there anywhere. You can't reference both. > Date: Tue, 5 Nov 2013 17:26:51 -0500 > From: yellowjacketl...@gmail.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

That third process has the type of commandline that is placed in the RunOnce key in case anything goes awry (reboot, BSOD, whatever) to facilitate attempts to recover/rollback/whatever when the system restarts. Something is running that commandline prematurely. Is it possible that some driver

Re: [WiX-users] Change Wix UI strings at run time

>From the MSI itself? You would have to relaunch the MSI from the beginning and >exit out of the running instance. Windows Installer's UI doesn't really >support that. That is one of the reasons why InstallShield always wraps their >MSIs in an EXE that lets you select the language (when you setu

Re: [WiX-users] platform x86 vs AnyCPU problems

WiX installation projects don't "produce" any applications (except for bundles). They just package them. Could it be that the two installers are capturing two differing instances of the application that happen to be tagged differently WRT bitness? Possibly the path to the application is comput

Re: [WiX-users] Change Wix UI strings at run time

Thanks Blair for the information. For example, i had added localized MST's to the main MSI file. When i run the MSI in a specific language like Italian, it will display the corresponding localized UI strings. Can't we handle localized MST's at run time by using Wix with custom actions? If this i

Re: [WiX-users] Change Wix UI strings at run time

Recently I also run into the same requirements. See this, http://msdn.microsoft.com/en-us/library/aa370074%28v=vs.85%29.aspx The MsiDatabaseApplyTransform's documentation mentioned, "This function cannot be called from custom actions. A call to this function from a custom action causes the funct

Re: [WiX-users] platform x86 vs AnyCPU problems

The same forms application is referenced by both installers. The reference "Full Path" reflects the build configurations. The PROD reference full path is bin/x86/prodBuildConfig/forms.exe and the TEST reference full path is bin/x86/testBuildConfig/forms.exe. All build configurations set the form