2. Bundles need to always be able to upgrade previous bundles. If that was
broken it'd be a pretty bad bug.
On Fri, Dec 14, 2012 at 2:54 PM, up2date.cyb...@gmail.com <
up2date.cyb...@gmail.com> wrote:
> 1. good
> 2. I was wondering if bootstrappers created with v3.7 (and installed on
> client ma
1. good
2. I was wondering if bootstrappers created with v3.7 (and installed on
client machines)
will be correctly updated when running a new bootstrapper created with
v4. In fact I was
talking about the client installation point of vue, not the development
part (like there won't
be duplicated a
1. I expect WiX v3.7 RTMs Christmas Eve.
2. I don't fully understand your second question. Bundles built using WiX
v3.x will work great. If you upgrade to WiX v4 toolset then you may have to
edit your setup code some to make it work because we may introduce breaking
changes in WiX v4 to make things
Hi,
Just wanted to ask the question below again.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: December-11-12 11:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Bundles in Bundles: How? (v3.7 wix Bundle Reference
Counting
Note: creating an executable over 200MB tends to have pretty poor launch
experience on Windows (especially if signed). Users often will launch the
executable multiple times because it takes a while for Windows to finish
all the verification.
On Thu, Dec 13, 2012 at 11:29 AM, Steven Ogilvie
wrote:
Did you put the CustomTable in your Bundle somewhere?
BootstrapperApplicationData is ignored when compiled into an MSI.
On Fri, Dec 14, 2012 at 1:26 PM, chefkoch wrote:
> Any suggestions, links or other infos how I could continue to get more
> infos into the BootstrapperApplicationData.xml?
>
>
Any suggestions, links or other infos how I could continue to get more
infos into the BootstrapperApplicationData.xml?
2012/12/12 chefkoch
> I am trying to create a custom table and making the content available for
> Burn/CustomMBA via the BootstrapperApplicationData.xml.
>
> When creating a cu
It will work if that column is marked "Formatted" in the MSI SDK.
On Fri, Dec 14, 2012 at 2:37 AM, Natalie Carr
wrote:
> Hi I am inserting the license agreement using tags with the rft
> formatting. It is showing up perfectly on the license agreement dialog.
> However I need to be able to pull
http://www.catb.org/~esr/faqs/smart-questions.html
> From: Chaitanya [mailto:chaita...@pointcross.com]
> Sent: Friday, December 14, 2012 7:46 AM
>
> Hi,
>
> How to add templates in wix.
>
> Thanks for help
>
> Chaitanya.
I cannot find a repro but I have created a new bundle and only included the
problem MSI and see exactly the same problem, so it would appear to be
something in the MSI that is affecting the detection. I believe this is the key:
Detected package: Setup, state: Present, cached: Complete
In
I've the same problem with build error. I have two wxl files for different
languages. With one wxl file it works,but if i add the second i got the
build error.
And is there any chances to localize the rtf license file?
--
View this message in context:
http://windows-installer-xml-wix-toolset.6
Hi I am inserting the license agreement using tags with the rft
formatting. It is showing up perfectly on the license agreement dialog.
However I need to be able to pull a property from the setup and use it in
the agreement, I am doing do but the agreement just shows with
[PROPERTYNAME] instead of
Hi there,
I do have a problem setting a property by the element filled
with a text from a locale file, cause it contains a new line.
Is there a way to escape the \r\n in the locale file so I can use it in
the element?
Regards
Michel
-
13 matches
Mail list logo
