Thanks I just tried it and it works :)
Much thanks!!
STeve
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: December-04-12 4:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing Pre-req from DownloadURL...
It is j
Thanks I just tried it and it works :)
Much thanks!!
STeve
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-04-12 5:06 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing Pre-req from DownloadURL...
The do
The download is used as runtime at build time burn needs to read information
from the file. I am not that familiar with the remote payload code but there
are examples in the source "src\ext\NetFxExtension\wixlib". If want a .NET 4.0
package you can also use the built-in code,
http://wix.sourcef
It is just needed during the compile so wix can gather the info it needs from
the file.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: December-04-12 5:37 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing Pre-req from DownloadURL...
If I
If I need to have that file in the same folder as bundle.wxs, what is the
point of using DownloadUrl?
I tried to use RemotePayload but was missing CertificatePublicKey,
CertificateThumbprint and most important Hash I looked at the .net exe it
was signed put the thumbprint was wrong and where do I
I'd say it cannot find the file 'dotNetFx40_Full_x86_x64.exe' - this needs to
be in the same folder as Bundle.wxs or you need to add a RemotePayload element.
Neil
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 04 December 2012 19:02
To: wix-users@lists.sourceforg
HI all,
I have my code like this:
http://go.microsoft.com/fwlink/?LinkId=223704";
Name="dotNetFx40_Full_x86_x64.exe"
InstallCommand="/passive /norestart"
Hi Rob -- I sent an email from my work address a while back, but I guess it
didn't get through.
Anyhow, yes I am interested. Probably better to use this address: wix at
rhysw dot com. Thanks !
-Rob Y.
Rob Mensching-7 wrote
> If you can wait a few more weeks, this might be an interesting thing t
That isn't supported but I think there is a feature request for it.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 04 December 2012 17:45
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Extracting embedded packages from the standard
bootstrapper
I th
Hello,
Does the bootstrapper return any error codes? (other than the log files)
If I have 6 pre reqs and my main installer, and one of the pre reqs fail,
the bootstrapper will fail, does it return any thing?
thanks,
Steve
--
View this message in context:
http://windows-installer-xml-wix-too
I third the request
Where does the /layout place the embedded apps?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extracting-embedded-packages-from-the-standard-bootstrapper-tp7578806p7582233.html
Sent from the wix-users mailing list archiv
On 04/12/2012 15:06, Rob Mensching wrote:
> Can you share a chunk of the log file for that. I expect the issue is the
> automatic retry code on errors is incorrectly catching this scenario.
[07E0:0640][2012-12-03T14:00:33]i301: Applying execute package:
package.msi, action: Install, path: C:\Prog
Thanks Rob. That pointed me in the right direction.
I changed to and it
seems to be working now.
On 04/12/2012 10:05 AM, Rob Mensching wrote:
> You probably have an external cabinet for your MSI that you need to include
> in the bootstrapper as well. If you use a Bundle to create the
> boot
Can you share a chunk of the log file for that. I expect the issue is the
automatic retry code on errors is incorrectly catching this scenario.
On Mon, Dec 3, 2012 at 6:15 AM, Bruce Cran wrote:
> Has anyone else found that the "cancel" button on the error retry dialog
> in WixStdBA doesn't work
You probably have an external cabinet for your MSI that you need to include
in the bootstrapper as well. If you use a Bundle to create the
bootstrapper, the toolset will automatically find all the external pieces
of your MSI. Otherwise, you have to track it all yourself.
On Mon, Dec 3, 2012 at 1:
Awesome. HexStyle was an "escape hatch" and I never tried masked edit
boxes. Glad it all worked.
On Tue, Dec 4, 2012 at 2:59 AM, Pawel Fujcik wrote:
> Setting HexStyle="0x20" on Editbox worked perfectly.
> Working code:
>
> TabStop="yes" FontId="5" FileSystemAutoComplete="no"
> HexStyle="0x20"
I would encourage you to think of the Bundle (aka: Burn) as your ARP entry
and the MSI(s) and other prerequisite executables as shipped contents.
You'll get a whole bunch of wins by using a Bundle if you can let go of the
fact that the MSI is no longer your ARP entry.
On Mon, Dec 3, 2012 at 12:1
The compress code comes from the VSSDK .zip creation functionality. Always
possible they have a bug in it.
On Mon, Dec 3, 2012 at 12:33 PM, Bruce Cran wrote:
> On 03/12/2012 20:16, Neil Sleightholm wrote:
> > I just tried again with 7-zip and do indeed get the "Unsupported
> Compression Method
Add this to ensure that the custom action data is hidden as well:
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Prevent-logging-tp7582177p7582224.html
Sent from the wix-users mailing list archive at Nabble.com.
>i am at loss to understand as to why would i have to test the results of
my immediate custom actions.
If nothing else for regression/bugfix validation purposes. If you are not
doing anything of complexity in the immediate actions, you need to decide
the value of testing overhead vs. risk for you
Setting HexStyle="0x20" on Editbox worked perfectly.
Working code:
#(loc.OptionsSQLServerAdminPassword)
Masked edit functionality in standard bootstrapper is working. Thanks a lot.
Od: Neil Sleightholm [n...@x2systems.com]
Wysłano: 4 grudnia 2012 11:36
D
The password style is ES_PASSWORD = 0x20, I have not tried this but it is worth
a go. I don't think you will be able to get the masked edit functionality
though.
Neil
-Original Message-
From: Pawel Fujcik [mailto:pfuj...@proximetry.pl]
Sent: 04 December 2012 10:24
To: wix-users@lists.s
I am using Wix 3.6 burn to install an exe package and I would like to have a
password editbox on the options page.
Options page in the file RtfTheme.xml looks like that:
#(loc.OptionsHeader)
#(loc.OptionsSQLServerAdminLabel)
#(loc.OptionsSQLServerAdminPa
Hello Steven,
As i am thinking more about this, i am at loss to understand as to why would
i have to test the results of my immediate custom actions.
For all i know, if any code changes in the installer result in any
undesirable changes, i would either ways catch it during my unit testing
phase r
24 matches
Mail list logo
