On 19-Jul-11 16:47, Nathan Coulson wrote:
> I was wondering if it was possible to disable SmartCabbing
>
> I use Wix 3.5 under linux, but it looks like wine may not have what
> wix needs to support this feature.
It can't be disabled (because of course it works on Windows). But I'm
not sure that's
On 19-Jul-11 23:35, Adam Langley wrote:
> Aside from a bootstrapper that runs the correct MSI, is there some accepted
> practice for achieving this with a single MSI?
No, nothing's changed. If you have to write to 64-bit portions of the
file system, you need a 64-bit .msi package.
--
sig://boB
On 19-Jul-11 12:25, Mark Modrall wrote:
> For #2, we have some installation stuff we only want done once (the stuff
> that the custom action does). So the first thing the custom action exe does
> is try to check the registry setting to see if it's been done (that's what's
> failing now). When
Hi guys,
We have recently developed a 64-bit version of our Microsoft Office plugin (now
that 2010 comes in both flavours), and would like to distribute a single
installer that installs the correct feature, based upon whether the user's
installation of Office is 32 or 64 bit.
Aside from a boots
What version of Burn?
On Tue, Jul 19, 2011 at 3:25 PM, JohnG wrote:
> That sounds familiar. A couple of years back we had a .NET app that would
> take a minute or two to start up without an internet connection. With a
> connection it took just a few seconds. If I remember right it was .NET 3.0.
That sounds familiar. A couple of years back we had a .NET app that would
take a minute or two to start up without an internet connection. With a
connection it took just a few seconds. If I remember right it was .NET 3.0.
--
View this message in context:
http://windows-installer-xml-wix-toolset.
I'm not sure what to look for in Process Explorer. CPU is basically 0%. If I
look at the Threads for Setup.exe (my bootstrapper), I see slow churning
activity for cryptnet.dll!I_CryptNetIsConnected and
CRYPT32.dll!I_CryptRegisterSmartCardStore. Green/red, loaded/unloaded, over
and over again
I was wondering if it was possible to disable SmartCabbing
I use Wix 3.5 under linux, but it looks like wine may not have what
wix needs to support this feature.
This was covered in a bug report I found,
http://bugs.winehq.org/show_bug.cgi?id=27133
where it sounds like the MsiFileHash table has
Have you run process explorer to monitor what is going on while they are
being cached?
Perhaps something else is accessing the files (i.e. AV software?)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Caching-payload-sudden-terrible-performance-tp65
Should there be any reason for the much slower times between these two log
files for caching payloads?
For example,
Total time caching payloads: 8 minutes (slower) vs. 21 seconds (normal)
Caching 2KB .REG file: 1 minute 18 seconds (10:24:32 -> 10:25:50)
Caching 1MB EXE file: 1 minute (10:25:50 ->
Hi Bob...
For #2, we have some installation stuff we only want done once (the stuff that
the custom action does). So the first thing the custom action exe does is try
to check the registry setting to see if it's been done (that's what's failing
now). When the custom action code is done, it se
Mark,
I would start with reading the following article.
http://www.installsite.org/pages/en/isnews/200108/index.htm
Regards,
Chris
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
On 19-Jul-11 11:10, Mark Modrall wrote:
> 1) Looking at the installer log, it's unpacking into a directory other than
> the INSTALLDIR; throughout I've been a little confused going to 3.5 about the
> relation of INSTALLDIR and TARGETDIR; did TARGETDIR supplant/replace
> INSTALLDIR? As noted bef
On 19-Jul-11 11:16, Dan Puza wrote:
> I have our prerequisites set as Permanent (SQL Server, .NET Framework,
> Windows Installer); and it would be confusing to suddenly have two ARP
> entries for the upcoming version our application, one from the bootstrapper,
> and one from the MSI.
Set ARPSYS
What I really meant is, is there a way to specify a title to be displayed in
the **standard RtfLicense bootstrapper application** (rather than having an
empty space where a title should go) without creating an Add Remove Programs
entry for the bootstrapper? (Bundle/@Name)
I have our prerequisi
Thanks Bob, that got the content into the installer package - which got me to
the point of trying to run it.
I ran into a couple of new issues
1) Looking at the installer log, it's unpacking into a directory other than the
INSTALLDIR; throughout I've been a little confused going to 3.5 about the
On 19-Jul-11 10:20, Mark Modrall wrote:
>Comments="bar" InstallerVersion="300" Platform="$(var.PPlat)"/>
Try Compressed="yes".
--
sig://boB
http://joyofsetup.com/
--
Magic Quadrant for Content-Aware Dat
On 19-Jul-11 09:15, Barry Wark wrote:
> I then run the command-line invocation via a custom action using
> [MATLABEXE] as the exe. This works well for finding a single Matlab
> installations under C:\Program Files\MATLAB, but the MATLABEXEproperty
> appears to get the path to only one installation
Use the command-line switch to candle. That will better prepare you for the
future.
On Tue, Jul 19, 2011 at 4:50 AM, Pally Sandher wrote:
> Alternatively
> http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/
>
> Palbinder Sandher
> Software Deployment Engineer
> T: +44 (0) 141 9
Why do you want to do this?
On Mon, Jul 18, 2011 at 9:38 PM, Bob Arnson wrote:
> On 18-Jul-11 19:12, Dan Puza wrote:
> > Is there a way to set the title of the bootstrapper without creating an
> Add Remove Programs entry for the bootstrapper?
>
> No, at least right now Bundle/@Name is what shows
Hi...
I'm trying to upgrade my Wix 2.0 installer scripts to Wix 3.5, and at
the moment I'm stuck on the fact that my product msi's are coming out
essentially empty and I don't see why. The individual merge modules look like
they're about the right size but none of the content is ending
I'm a relavite newbie with WiX, but haven't been able to figure out
the answer to this question via Google or StackOverflow (for the
record, the question is posted at
http://stackoverflow.com/questions/6710578/multiple-results-for-wix-findfile;
I'll update with any answers received here):
I'm tryi
Alternatively
http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registe
You need this:
-Maksim
-Original Message-
From: Ravi Gupta [mailto:ravigupta...@gmail.com]
Sent: Tuesday, July 19, 2011 2:32 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Install Files in C:\Program Files\ folder in 64bit-Win7
I created a setup for
Set the Platform attribute on your Package Element to "x64" rather than "x86"
and/or create an "x64" platform build configuration in your .wixproj to build
an x64 MSI. You need separate x64 & x86 MSI's if you want to target x64
locations on x64 systems.
Palbinder Sandher
Software Deployment En
I created a setup for 64 bit OS using wix, but when I try to install
in C:\Program Files\ instead it is installing in C:\Program Files(x86)\
folder.
how to rectify this.
my code goes something like below:
Hi,
I faced the problem what you mentioned below. My project MSI is
comprised of many merge modules. So I can't create patch in the method
you suggested.
So I tried a different method for creating the patch as shown below.
patch.wxs:
http://schemas.microsoft.com/wix/2006/wi";>
If you build the project within votive then add the different wixlibs
for x86 and x64 in Project Properties -> Tool Settings -> Additional
parameters -> Linker
Adding them directly as reference in the Setup Project not possible as
there are needed different ones for x86 and x64.
2011/7/19 Tobia
Not possible as you need OS type dependent DIFx libraries in the
resulting installer. You can simplify that by include different
fragments for x86 and x64 DIFx drivers like e.g. the following sample
feature:
Driver_x64.wxs
---
http://schemas.microsoft.com/wix/2006/wi";
xmlns:difx="http://schem
Thanks! THats what i needed.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: lunes, 18 de julio de 2011 20:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Including a file but not installing it via a
feature? -- ICE21: Co
30 matches
Mail list logo
