Hi,
I am making a bundle with Burn which chained few packages. It is working
fine for admin users but for non-admin I have few requirements.
Some included packages require elevation but they are not necessary. So for
non-admin I want to just skip them gracefully without asking for elevation.
I tr
There are number of ways of achieving results results.
1) As told by Gabriel
2) Don't include -srd switch to harvest root directory as element.
3) use -var in Heat and -d in candle.
e.g for 3
heat.exe dir "$(SolutionDir)MyProject\MyDirectory" -ag -sfrag -srd -var
"var.MyProjectDir" -out $(ProjectD
Although that was not required but unfortunately I have to *either *put them
on remote location and include them as downloadable payload in setup to
reduce the package size.
*Or *to include them in the package by compressed="yes"
--
View this message in context:
http://windows-installer-xml-wi
Hi folks,
I am using WIX 3.7...
I have replaced the default BMP for our companies version: and
I am using Windows 7 Enterprise 64 bit, when running the resolution at
Smaller 100% (Control Panel -> Appearance and Personalization -> Display)
the top/side banner looks great...
However when runni
I have already started discussion with the vendor...
Thanks for the advice...
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: February-07-2013 3:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Third Party Merge Modu
Using WIX and the Windows Installer you cannot mix 32 bit and 64 bit files,
whomever created that 3rd party merge module shouldn't have mixed 32/64 bit
period...
You will have to have a 32 bit MSI and a 64 bit MSI, use burn to install them.
Steve
-Original Message-
From: Marc Beaudry [
I understand that I will end up with a 32bit package only ion the end, but
VS 2010 accepts this 3rd party MSM file and builds its 32 bit package with
complaining.
Wix is reporting this ICE80: error. Is there not a way I can have wix do
like visial studio, simply include the MSM and use the 32bit
This is dangerous territory. The docs explicitly say you can't do this:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367451(v=vs.85).as
px
And generally you need two MSI files for different architectures:
http://blogs.msdn.com/b/heaths/archive/2008/01/15/different-packages-are-req
I am attempting to add an image that will act as a background for each burn
page. If I only define the image in one page it will sometimes work, other
times the controls on the page will be overwritten by the image. If I add an
image to each Page then no controls appear until they receive focu
Hello
I have a third party merge module returning this error:
error LGHT0204: ICE80: This package contains 64 bit component
The error refers to a registry component. My installer is 32bits and needs
to remain this way. I initially had an installer built with VS2010 and all
this worked fi
Are you able to start/stop the service manually? Just to make sure there's
nothing wrong with the service itself. What is the exact error message
you're seeing? Is there anything in the Windows event log? Such as a
permission issue?
--
View this message in context:
http://windows-installer-xml-
WiX requires that anything you actually reference does really exist
somewhere. That's a general rule that you should focus on. I Darked many
MSIs and got this type of error because many other tools don't check that
something you use (such as a custom action) is actually specified somewhere.
So wh
Hi All,
This is the first time I am using Dark.exe to decompile my existing MSI file.
After it generated source setup file I tried to compile generated source(*.wxs)
file which gave me following error :
Error 4 Unresolved reference to symbol
'CustomAction:WEBCA_CreateURLs' in
Ahhh, my understanding was the name was the location where the directory
gets created, obviously I was incorrect.
Thanks for the reply, I will look up your proposed method.
($(var.manufacturer))
Marc
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Februar
You can't use properties as directory names because the type of the Name
attribute is LongFileNameType, not Formatted (see the Wix help), and property
names are not substituted except in formatted types. Even if you could do it,
it would be a bad idea because it would break the auto component guid
Hello
I am new to wix and just finished the tutorial, I am now experimenting with
things.
When I run my MSI I get a literal [Manfacturer] as a folder instead of the
assigned manufacturer name set in the Product tag.
I tried [ProductName] and I get the same r
If you need directories that you can set yourself, use a structure like this:
If no properties are passed on the command line, the structure above is used:
the website goes into [ProgramFiles]Chaitanya\website and the otherfiles go
into in
Hopefully someone can help me on this.
I just upgraded from WiX 3.6 to 3.7. In my bundle I use a wxl file to
localize the prerequisites installer to German like this:
This worked fine on WiX 3.6 and stopped working after upgrading to WiX
3.7. I know that WiX 3.7 comes with a bunch of l
18 matches
Mail list logo