He may want to keep the 32-bit (if he has one) from running on x64,
though -- in which case:
Neil Sleightholm wrote:
> Why not just make your msi 64 bit, that will only allow installation on 64
> bit platforms.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n
I don't know that I'd really agree with that priority. A bootstrapper is
really not that hard to write to start with.
Arun Perregatturv wrote:
> Brian,
>
> I would vote for Burn to kick start sooner than other things. The most
> important thing for any or all installer is the BootStrapper witho
God, I love letmegooglethatforyou.
Rob Mensching wrote:
> http://www.letmegooglethatforyou.com/?q=wix+major+upgrade
>
>
> -Original Message-
> From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
> Sent: Tuesday, January 06, 2009 09:42
> To: General discussion for Windows Ins
Rob Mensching wrote:
> There is no file searching during the build process. Does the C++ or C# or
> VB compiler search for things during compile? I think you need some
> makefile/nant/msbuild logic that passes defines to the compiler to get what
> you want.
>
This is exactly what we do her
I had a similiar problem with a C++ custom action that needed to display
a confirmation dialog. ::MessageBox() had the same issue, so I had to
switch to using MsiProcessMessage from the Windows Installer API. This
worked out fine for me, but in your case, I think you're stuck. MS puts
a lot of
If you run misexec by itself it will give you a list of valid
parameters. "/l foo.log" gives you pretty much minimum verbosity
Yu, Brian wrote:
> I got this from http://www.dalun.com/wix/06.26.2005.htm
>
> c:\WiX\msiexec /i product.msi /L*v log.txt
>
>
>
> Is this the only way to write out lo
w->Summary Information on the MSI in
question, and found that the available platforms were not what I expected.
Michael Owings wrote:
> I'm actually using V2 for now. The odd bit is the failure when I use x64
> for the platforms attribute; that just seems weird unless it dislike
32-bit MSI on an X64 platform. Windows Installer does this
automatically. I believe you have to build a 64-bit MSI.
Nic Barden wrote:
>
>
> Hi all,
>
>
>
> I have an urgent requirement to fix an issue to do with the path to the
> program files directory.
>
> I am testing an app that perfo
I just wrote my own. All you need is a stub exectuable that knows how to
extract and execute resources from its own image, plus a program to
embed the resources into the stub.
Others have mentioned that winrar has the capability to build a simple
bootstrapper exe, custom icon and all. You give
I had this problem a while ago. From looking at the logs, it turned out
that the underlying file the shortcut referred to could not be
uninstalled because of an issue with the old product uninstall. Because
of that, the old shortcut was not removed. My guess is that something is
breaking on you
I think the first issue is caused by the Wix utility static libraries
being build with VS 2008. You'd need to rebuild them with 2005, I
believe. This isn't a problem with 2.x (and VS 2005).
Curtis Jewell wrote:
> 1. I'm trying to write a custom action, and bug 2166658 is hitting me
> despite upg
You'll never get a 32bit installer to validate with 64
> bit
> components in it, period. MSI requires that you build a single
> installer for each architecture you target. You can use conditional
> statements and variable replacement in your .wxs file to have a single
>
2
> bit system anyway, so just don't include those components in your 32 bit
> installer, or alternately, don't offer a 32 bit installer. In some
> corporate environments, that might work.
>
> Chris
>
> On Tue, Oct 28, 2008 at 9:19 AM, Michael Owings <[EMAIL PRO
Pally Sandher wrote:
> Yes but you will get an ICE80 error when compiling if you set
> Win64="yes" on a component when your MSI is an x86 build & vice-versa.
>
> Why would you want to?
If you install mixed 32 and 64-bit components in a single install? We
have an installer that MUST do this. Wha
No need to go to 3.x.
For 2.x just try editing the project files directly. Like all recent VS
project files, they're just xml.
I changed my output directory this way (to get rid of the bin
directory). You can probably just change the Configuration elements to
get rid of the obj directories as
Works perfectly -- thanx.
Rob Mensching wrote:
> Use MsiProcessMessage() and the right thing happens.
>
> -Original Message-
> From: Michael Owings [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 22, 2008 13:56
> To: General discussion for Windows Installer XML
I have some C++ custom actions in my installer that will occasionally
pop up message box warnings or prompts. I'm using NULL (Desktop) as the
parent window handle for these message boxes, but under vista, they tend
to show up hidden beneath the main WIX ui. Is there a way to get a
useable windo
Custom action?
Kalvagadda, SivaKrishna (MLX Technology) wrote:
> Is there any other way to create Group?
>
> Regards,
> SivaKrishna Kalvagadda,
> 201-671-5552.
>
> -Original Message-
> From: Rob Mensching [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 21, 2008 1:09 PM
> To: General
It's also worth noting that it's not awfully hard to write your own --
which has some advantages, in that you can customize it to your liking.
I just wrote one for our own project this morning.
Basically you'll need to produce an executable stub (with no external
dependencies) that knows how to
If they're not that picky, there's always the installation log. Ithe log
also has the advantage of being pretty precise as to the changes made.
Chris Mumford wrote:
> I've got a customer asking me what files and registry values my installer
> creates. I'm thinking of something like MakeMSI's inst
olset.
> Subject: Re: [WiX-users] 64-bit installer questions (simple)
>
> I don't really know anything about 64-bit installations but as far as I can
> see there is a 64-bit version of wix..perhaps that might help?
> http://wix.sourceforge.net/releases/3.0.4603.0/
>
> 2
Due to some kind of issue with a major upgrade breaking (To wix from an
existing IS install), my Wix install is broken. I'm getting the dreaded:
MSI (s) (BC:C8) [16:09:18:281]: Disallowing uninstallation of component:
{93426E57-F227-48BA-94D7-BCBC7A2E86D3} since another client exists
MSI (s) (BC:C
Martin MacPherson wrote:
> I don't really know anything about 64-bit installations but as far as I
> can see there is a 64-bit version of wix..perhaps that might help?
Hmmm -- dunno. Make sense to anyone else?
>
> http://wix.sourceforge.net/releases/3.0.4603.0/
>
> 20
This is certainly more of a Windows Installer question, but here goes:
1) I've noticed that my MSI will not run on a Vista-64 box if I add the
Platforms="x64" attribute. The error is something to the effect of :
"This installation package could not be opened. Contact the application
vendor to v
> -----Original Message-
> From: Michael Owings [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 14, 2008 1:11 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Major upgrade from an IS12 installer project
>
> I am in the processing of movin
d to preserve whitespace when parsing... In all
> likelihood Wix isn't doing that, but it is conceivably possible...
>
> Mark
>
>
> -Original Message-
> From: Michael Owings [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 14, 2008 4:41 PM
> To: General
If you're trying to format the xml itself, you may be out of luck --
msxml (which I believe wix is using) will do the formatting however it
feels like doing it. This is true of most programmatic xml access.
If the text in question is in a CDATA section, however, I'd think that
should work, assu
I am in the processing of moving from IS12 to Wix for a number of our
products. So far, things are going fairly well.
There is one issue, however. The install we have out in the field is
version 4.0.17. I have done a Wix installer that does a major upgrade to
4.0.20. Everything works fine -- th
I believe you can just change the value of the $(WIX) environment
variable to point to the right place (at least this is the case with 2.0)
Neil Sleightholm wrote:
> I have just updated to WiX v 3.0.4603.0 and the install location has
> changed, it was "C:\Program Files\Windows Installer XML Tool
I believe it is also possible to bypass the maintenance screen by simply
passing /qb to misexec. This should give you a progress bar and cancel
button, but that's it -- the upgrade happens with no user intervention:
msiexec /i ExampleInstaller.msi /qb REINSTALL=ALL REINSTALLMODE=vomus
I could b
reserve all the
> GUIDs for you. Technically speaking, you should be able to switch at any
> time and rebuild a functionally identical MSI file (although it may be a
> little smaller since WiX tries very hard to only add the things you need).
>
> -Original Message-
> From
It seems as if it would be vastly simpler to write the stub installer
yourself -- it's hardly doing anything, other than checking two
conditions and launching (or not launching) another executable (or in
this case, MSI).
Kunal Manaktola wrote:
> Hi I'm new to WiX and I just a have a few questio
This is how I generally do it (message box/attach debugger) -- although
you can of course do your own logging.
You could probably even trigger it off of a property passed on the
MSIEXEC command line.
John Hall wrote:
>> Yeah, Windows Installer doesn't let it work. Why? Some
>> message process
> Installer rules for upgrades. Major upgrade? Change the ProductCode... etc.
>
> 3. Dark.exe can help get all of your authoring and it will preserve all the
> GUIDs for you. Technically speaking, you should be able to switch at any
> time and rebuild a functionally identical
I'm currently in the process of moving from an InstallShield 12 (which I
loathe) project over to wix. I'd ideally like to be able to update the
next version of this project via wix.
I'm wondering if I use the the same product and component IDs if I'd be
in good shape as far as an upgrading goe
OK -- scratch that. The issue was that I needed to define the computed
directory property on the MSIEXEC command line so that it went under the
before/after directory. Once that happened Msipsp picked up the files
and upgraded them just fine.
Seems to work well now
Michael Owings wrote
Probably more of an MSI question, but here goes:
I have a wix-produced installer (2.0) that I'd like to create a patcher
for. While I can always upgrade via MSI, there are times when being able
to use the patcher would be nice.
So as I understand it, we create two administrative installs with t
Is XMLFile supposed to back out any changes made to an xml file on
uninstall (I'm using wix2)? If not should I be using xmlConfig?
--
Teleoperate a roving mobile robot from the web:
http://www.swampgas.com/robotics/rover.html
--
This is probably a stupid question, but I have a wix-based install that
executes a flash installer if the current flash version is below a
required version. Everything works fine, but I'd like to remove the
installer after execution. Is this possible? I looked at RemoveFiles,
but this doesn't l
39 matches
Mail list logo
