WiX v3.x we turned on validation by default. That can be very slow. The
"-sval" switch will disable it to get a more apples-to-apples comparison.
On Wed, Feb 15, 2012 at 2:52 PM, Andrew J. Dalgleish <
adalgle...@santanderconsumerusa.com> wrote:
> I have a question regarding performance, as we mov
Can you add the per-user details to the bug so we don't forget.
On Wed, Feb 15, 2012 at 2:19 PM, Peter Hull wrote:
>
> Actually that turned out to be a red herring. I think the real cause is
> (as you suspected) the InstallScope. I only see the error for perUser MSI
> packages. I am using WinXP
You might try organizing your builds into .wixlibs. A .wixlib can integrate
at more touch points than a Merge Module can.
On Wed, Feb 15, 2012 at 12:21 PM, Christopher Painter wrote:
> A merge module is reusable and doesn't know about INSTALLDIR or TARGETDIR.
> It know's about ModuleRetargetableD
Pick a different bootstrapper or wait for Burn to support the feature (but
that won't be until WiX v4, at best). Sorry.
On Wed, Feb 15, 2012 at 7:37 AM, Rody, Herbert M (Marshall) <
marshall.r...@intergraph.com> wrote:
> Thank you so much for your time and reply.
>
> Would you be able to suggest
I have a question regarding performance, as we move from an earlier version of
wix 2.0.5325.0 to the current stable build.
A little background on how we use wix:
We start with a very simple xml file, which contains only the essential things
that define what goes in the msi.
Here is what a website
Actually that turned out to be a red herring. I think the real cause is (as you
suspected) the InstallScope. I only see the error for perUser MSI packages. I
am using WinXP so maybe that is why you can't reproduce it?I appreciate your
help on this, thanks.Pete
--
A merge module is reusable and doesn't know about INSTALLDIR or TARGETDIR.
It know's about ModuleRetargetableDir. When you consume the merge module
in an installer you will use a Merge, MergeRef and Directory element
combination to associate the ModuleRetar.. to INSTALLDIR or INSTALLLOCATION
Hi,
I'm using WiX 3.0 and utilizing heat.exe to harvest a directory in my build
tree. My goal is to generate a MSM using the resulting .wxs file. I have a
couple of MSIs that will use this MSM, and each MSI will want to install the
MSM files into a separate directory. Here's my problem:
- B
Please add that to the bug...
On 15-Feb-12 11:57, Peter Hull wrote:
> I've done a bit of playing around and it seems to be linked to install
> conditions, i.e. if I change my bundle's chain to
>
> InstallCondition=" 1 " />
> InstallCondition=" NOT 1 " />
>
I've done a bit of playing around and it seems to be linked to install
conditions, i.e. if I change my bundle's chain to
it works, even with these 'silly' conditions.
> Date: Wed, 15 Feb 2012 10:43:09 -0500
> Fr
On 15-Feb-12 10:15, Rob Mensching wrote:
> File a bug, but I'm not exactly sure how to investigate. I'm (obviously)
> not seeing the same problem. And if you're installing the WiX toolset,
> then you aren't either (at least once).
Both bugs involve per-user packages...
--
sig://boB
http://joyofs
On 10-Feb-12 12:03, David McCabe wrote:
> I'm having a few problems with dark. The MSI I'm attempting to decompile was
> built with WiX 3.5 and a modified form of WiXUI_InstallDir, by copying
> WiXUI_InstallDir.wxs into a section and modifying:
Did you keep the WixUI_Mode property? The UI extensio
Thank you so much for your time and reply.
Would you be able to suggest a possible approach I could use?
Kindest Regards,
Marshall
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, February 15, 2012 9:19 AM
To: General discussion for Windows Instal
Okay, weird. I'm not seeing this behavior so I'm a bit perplexed how it is
happening. Can you provide detailed repro steps? Do you already have the
Bundle installed when installing again? ... uhh, I'm grasping at straws on
this one.
On Wed, Feb 15, 2012 at 4:57 AM, Peter Hull wrote:
>
> OK I h
The list is coming from the file itself. The languages in the MSI is
supposed to match the file so the WiX toolset helps you do that.
Unfortunately, the Windows Installer team didn't make that column wide
enough for files that support *lots* of languages.
On Wed, Feb 15, 2012 at 4:54 AM, Parkes,
Burn (unfortunately) does not yet handle instance transforms. Switching
from the "non-transformed" MSI will confuse Burn currently. Something we
need to address but just won't get it in the first version.
On Tue, Feb 14, 2012 at 8:51 AM, Rody, Herbert M (Marshall) <
marshall.r...@intergraph.com> w
Strange. What does the plan show as the state for all these packages?
On Tue, Feb 14, 2012 at 11:41 AM, Ian Williams wrote:
> I have wixstdba bundle with MSI packages A, B, C, D, E. They are all
> marked as vital and the chain explicitly says DisableRollback="no". There
> are no RollbackBoundar
File a bug, but I'm not exactly sure how to investigate. I'm (obviously)
not seeing the same problem. And if you're installing the WiX toolset,
then you aren't either (at least once).
On Tue, Feb 14, 2012 at 8:09 AM, Peter Hull wrote:
>
>
> I've rechecked and it works fine on the beta version
I'm seeing an issue where the installer is occasionally leaving behind
empty folders even though the log reports that they are being deleted.
I have some shortcuts on the Start Menu, For each folder there is a
component containing a RemoveFolder item, and the component for each
shortcut also c
Ok, so here is a final, tested and fully working solution, which also
takes into account a previously installed version, so in case of an
upgrade the already installed location is used by default. The steps
below are in the order of execution, figured out from the msi logs.
All of this is under a B
OK I have filed a bug:
https://sourceforge.net/tracker/?func=detail&aid=3487838&group_id=105970&atid=642714
I've tried to include your information, please add/correct as appropriate.
Peter
> From: hkra...@infinitec.de
> To: wix-users@lists.sourceforge.net
My installer includes a pair of DLLs each with a set of MUI localization files.
Each of the DLLs is generating a warning on the element:
ICE03: String overflow ... Table: File, Column: Language
When I look at the resulting file table in Orca, I can see each of the language
IDs for the MUI fi
Well, I'd still disagree, but eitherway you'll need a custom action. MSI
doesn't have any built in expressions for lowering the case of something.
The closest it has is the ability to specify if a equality check is case
sensitive = or insensitiive ~= .
---
http://netsuae.com/modules/mod_wdbanners/friends.php?arent164.html
--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cl
Dear Henning,
I think this is the same problem I have seen and reported recently to this list:
http://sourceforge.net/mailarchive/forum.php?thread_name=DUB101-W57E6E77EDBB70153F4CD0CAD7C0%40phx.gbl&forum_name=wix-users
I think it really is a bug (the 3.6beta worked for me) so I will file one on
I'm using WiX v3.6.2610.0
Test platform: Windows 2003 x86 en, latest service pack
I created a Burn Bootstrapper which installs one MSI as "Per User". Depending
on the state of the target machine, some prereqs have to be installed
per-machine.
So I created this bootstrapper:
http://s
26 matches
Mail list logo
