Have you filled the ThemeFile Attribute with your theme file?
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication
ThemeFile=theme.xml
LicenseFile=License.rtf/
/BootstrapperApplicationRef
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
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
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
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:
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
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
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
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:
Classification: Public
No you don't need to physically copy the wxs file, you just need to copy the
UI element from that wxs file into your code. Then you need to add your dialog
I.e.
DialogRef Id=MyNewDlg/
You can substitute your dialog for the LicenseAgreementDlg dialog...
i.e.
UI
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...
UI Id=WixUI_Minimal_Modified
In my Product.wxs I added...
UIRef Id=WixUI_Minimal_Modified/
If I
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
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
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 phogl...@rimage.com wrote:
The CHM, the Wix tutorial, and searching this
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:
Search your entire installer source code and make sure there isn't another
UIRef 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:
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 setup
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
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
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
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 forms
21 matches
Mail list logo
