The WixBA at src\Setup\WixBA is the C# managed BA that is used by the
installer that installs the toolset. The Bundle does not have a
bal:Condition in it and as far as I can tell there is nothing directly
related to Bal:Condition in WixBA. However I think what folks have
suggested is that one
Blair, sorry to bother you. I ran the log file on windows xp and got same
results and 'Assets' folder got removed. So why not on win 7?
Thanks,
Balu
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Thursday, August 01, 2013 10:39 PM
To:
Hi Phil,
Glad to help, and thanks for the suggestions. It does make sense to localize
the theme itself, though I have not done so yet. Did you try it?
Alnoor
--
View this message in context:
My experiments so far do not work. I added:
Payload Id=themeXml_de_de Compressed=yes
Name=1031\HyperlinkTheme.xml SourceFile=theme\1031\HyperlinkTheme.xml/
And made various changes to only that xml file, but so far it has not picked
it up. I was just starting to read through the source code,
We have the following scenario:
- base installation with 14k files, 800MB msi file and about 1,4GB after
installation
- patch changing about 2k files and adding 13k files, 400MB msp file
- base installation took about 5-7 minutes to install
- patch took more than 40 minutes to apply
It looks like the answer to loading a localized xml file is here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localized-bundle-Picking-up-the-right-files-td7265208.html
I have not tried it yet, but he is correct that I did not have the png file
in each localized folder.
--
The goal is to set the installation directory to C:\Program Files\Ent Federal
Credit Union\ProductName
This produces a build error:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFiles64Folder
Name=ProgramFiles
MSI's code is different between different platforms. You could file a bug with
Microsoft.
Sometimes adding a CreateFolder or RemoveFolder fixes these things. Try the
CreateFolder first.
From: balu.mam...@flightsafety.com
To: wix-users@lists.sourceforge.net
Date: Fri, 2 Aug 2013 10:15:44
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFiles64Folder Name=ProgramFiles
Directory Id=Us Name=Company
Directory Id=INSTALLLOCATION Name=LogonTimerService/Directory
/Directory
/Directory
/Directory
Directory Ids are always MSI session Properties, so don't allow
It means what it says. There's already a Manufacturer property. I use the
Directory@Id CompanyFolder. Rather than go through all the machinations, use
WixUI_InstallDir and let it adjust your INSTALLLOCATION.
There's documentation on this in both the WiX help and the on-line tutorials.
--
If it's a data file the MsiFileHash table may need an update. MsiFiler.exe
from the Windows SDK might be useful.
Phil
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: Thursday, August 01, 2013 6:57 AM
To: chr...@iswix.com; 'General discussion for
If the problem is actually related to the event log source, then back to
John's question: What does NETFRAMEWORK20INSTALLROOTDIR64 evaluate to?
The log fragment you show isn't obviously anything to do with the event log
- it seems to related to TARGETDIR and Windows perhaps trying to resolve
What does your patch log show as being the places that more time is used? You
can compare the install log and patch log to see where the differences in
processing are occurring.
Unless you have RemoveFile operations that run at install (as opposed to
remove) then there shouldn't be any
The error message should be different. Please file a bug.
Date: Thu, 1 Aug 2013 08:34:52 -0700
From: phogl...@rimage.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange
error
VS2010/Votive displays bal:Overridable as an
Cool, thanks. If worst comes to worst, I'll just fire up Process Monitor
again and watch the file system activity to see what files the bootstrapper
is looking for (and not finding.)
Somehow, that feels more fun than wading through source code.
Alnoor
--
View this message in context:
I'm sorry, I have looked at the bug tracking page (and other tabs) and I
don't see how to file the bug. I would like to understand how to do it.
--
View this message in context:
Well I got it working. As posted earlier I added a modified
HyperlinkTheme.xml to my 1031 subfolder, and originally I added this Payload
statement:
Payload Id=themeXml_de_de Compressed=yes Name=1031\thm.xml
SourceFile=theme\1031\HyperlinkTheme.xml/
The bundle project builds but when run it
I don't really understand your suggestion.
I have 18 tabs of google searches open, and reading the WiX help, and looking
at the source code for four days now.
Finally found this:
On Tue, 30 Jul 2013 21:50:54 -0700, Blair Murri wrote:
You can use the MajorUpgrade element (use the UpgradeCode you prefer in your
Product element) and
use just the offending UpgradeCode in the Upgrade element (to find/remove
versions using it).
Blair,
I tried that but end up with two
You have to create an account and log in and then you see button to create a
bug. IIRC.
Wes
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: August-02-13 3:36 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes
Bug created. Thanks for the help. Someday I hope to help fix the bus.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767p7587800.html
Sent from the wix-users mailing list archive at
I like that way.
On Fri, Aug 2, 2013 at 12:51 PM, Tony White twh...@ent.com wrote:
I don't really understand your suggestion.
I have 18 tabs of google searches open, and reading the WiX help, and
looking at the source code for four days now.
Finally found this:
This is related to:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html
but I thought it best to start a new thread.
Using VS2010 3.7.1224 WixStandardBootstrapperApplication.HyperlinkLicense
project, I added the following
You must log into Sourceforge.net using the account you possibly setup when you
added yourself to the wix-users list. Once you are logged in, there is a
Create ticket button that shows up between the search box and the View Stats
button along the left edge of the main box in the window.
Date:
MajorUpgrade places common (usually two) rows into the Upgrade table using the
UpgradeCode specified in the Product element. One is used for removing previous
product versions and the other row is used for preventing downgrades.
The additional Upgrade element needs an UpgradeVersion child
I saw a prior post and created a Sorceforge account and then created the bug.
But it is different from the one I was logged into the forum with. In the
future I can use the forum login. Sorry for the confusion.
--
View this message in context:
Make the payload (localized) WXL files of type None (using the property area
in the lower right corner of the IDE).
Date: Fri, 2 Aug 2013 14:07:15 -0700
From: phogl...@rimage.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [Votive/Light] LGHT100 error when more than one
Hi,
I have been trying to add Downgrade support to our MSI. I know
Uninstall/Re-install is preferred over this, but this is needed for automated
deployments and is specially helpful for our zero-downtime product upgrades
across multiple machines. So the requirement is that any version can be
Are/will any of the binaries you distribute in this product (or ever intend to
distribute) ever [be] distributed by any other product?
From: surya6...@hotmail.com
To: wix-users@lists.sourceforge.net
Date: Sat, 3 Aug 2013 04:39:26 +0530
Subject: [WiX-users] Adding Downgrade support to MSI
No, the binaries are specific to a product only and will never be distributed
by any other product.
From: os...@live.com
To: wix-users@lists.sourceforge.net
Date: Fri, 2 Aug 2013 20:05:21 -0700
Subject: Re: [WiX-users] Adding Downgrade support to MSI
Are/will any of the binaries you
The primary problem with amus is when it is used with anything shared (e.g. the
VC merge modules).
A secondary problem exists with large MSIs where it causes repairs (and
patches) to take longer to run, or where custom actions that use component
states are needlessly rerun in patches and
31 matches
Mail list logo
