Those settings are read from the registry in the msbuild .targets file if
the values for the variables are not provided in the msbuild environment.
For instance, see C:\Program Files
(x86)\MSBuild\Microsoft\WiX\v3.5\wix.targets, and look for the task
_SetDefaultPathValues.
If you want to use
I'll repeat it again, in case it got missed earlier.
I'd recommend looking at the output of sxstrace to see why it's not
locating the assemblies you expect. That should be enlightening. I'd
expect it to tell you exactly where it looked and why it didn't find what
it was looking for
Have you used fuslogvw (the fusion log viewer) to try to see what's going
on, or the sxstrace tool?
I'd recommend looking at the output of sxstrace and/or fuslogvw to see
what's happening. I'm pretty sure it'll be enlightening.
Kelly
Christopher Painter chr...@deploymentengineering.com
I can't speak for everyone else, but it's always worked fine for me, I get
my own messages within 10 minutes or so of sending them.
Kelly
Bill McCormick wpmccorm...@sbcglobal.net
03/22/2010 12:29 PM
Please respond to
General discussion for Windows Installer XML toolset.
Do both of your installers use the same component ID for that DLL?
Robert Barnes robert.bar...@gmail.com
01/14/2010 11:53 PM
Please respond to
General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
To
wix-users@lists.sourceforge.net
cc
Subject
[WiX-users]
Why are your two upgrade codes different? Are you doing that on purpose?
The upgrade code should remain the same for all products that are
considered to be in the same upgrade family.
by two upgrade codes, I mean the UpgradeCode in your Product tag and the
Id in the Upgrade tag.
Giora
Are you using the same component GUID for each of these keys? You can't
do that... It's breaking the component rules and all kinds of bad things
happen when you break the component rules.
Each distinct component keypath (the 'main' entry in a component) MUST
have a unique component GUID.
I wasn't asking about ProductCode. I'm asking about the component GUID
for the registry key you're referring to. You need to assign different
GUIDs for all components that could be installed in two locations by the
two different instances. If you want to install the same files in two
This isn't a WiX problem. It's MSI, and there's nothing you can really do
about it in the setup authoring, as far as I know. The only way I'm aware
of to change it is to use MSIEXEC command line parameters to tell MSI to
overwrite changed files.
You should really look into using patches or
We have an installer that I built on an earlier version of WiX 3.0. I'm
now looking to upgrade to a more recent WiX because I need to work on
installer work again. I'm using VS2008, but I do most of my WiX stuff
from the command line.
Should I be getting 3.0 latest, 3.5 latest, or is there
Colin,
When you say setting the 'OutputName' field do you mean through the UI
or through manually editing the project file. Theoretically, you should
be able to edit this in the project file and it will work (using the
'$(xxx)' syntax), but the VS IDE doesn't let you do so through its own UI.
Shouldn't that be Relative not Realtive?
Andreas Owen ao...@1eeurope.ch
01/20/2009 12:05 AM
Please respond to
General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
To
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
cc
Subject
[WiX-users]
ComponentGroup is a wix concept, not an MSI one. It's just for the
organization of your wix files. You may have as many components per
component group as you like, as far as I can tell, we've got many hundreds
(I think, never really counted) in one of ours.
Kelly
Arun Perregatturv
Sounded to me like he was trying to get around the limitations of MSI, not
CAB. He wants to be able to include a full directory in the MSI without
putting the files in components. This is not possible with MSI and
doesn't even make sense given the way MSI is designed. Also, the scenario
he
Robert, your best bet if you're building a C/C++ custom action is to use
static linking so you don't have any dependencies.
Kelly
Robert Barnes robert.bar...@gmail.com
01/05/2009 11:09 PM
Please respond to
General discussion for Windows Installer XML toolset.
Oren, you should include tools.dll as a resource inside CustomActions.dll
(or just include it at the end of the file using some mechanism whereby
you can pull it back out), and then extract it to a temp folder during
your initial processing in CustomActions.dll and load it using
LoadLibrary.
Installer XML toolset.
wix-users@lists.sourceforge.net
To
General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
cc
Subject
Re: [WiX-users] Bitmaps and License file on custom UI's?
Kelly Leahy wrote:
DefineConstants=$(BuildDefineConstants);WixUIBannerBmp=Setup
:[EMAIL PROTECTED] От имени Kelly Leahy
Отправлено: 16 сентября 2008 г. 19:53
Кому: General discussion for Windows Installer XML toolset.
Тема: Re: [WiX-users] HA: Bitmaps and License file on custom UI's?
That would only fix the one dialog that I'm defining. it won't fix the
other 6 or so
= WixUI_Bmp_Banner .
Regards,
Denis Zavorotnyuk.
-Исходное сообщение-
От: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] От имени Kelly Leahy
Отправлено: 16 сентября 2008 г. 3:43
Кому: wix-users@lists.sourceforge.net
Тема: [WiX-users] Bitmaps and License file on custom UI's?
I have
for this picture
instead of WixUI_Bmp_Banner ?
Regards,
Denis Zavorotnyuk.
-Исходное сообщение-
От: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] От имени Kelly Leahy
Отправлено: 16 сентября 2008 г. 19:08
Кому: General discussion for Windows Installer XML toolset.
Копия
I have overridden the default UI by doing the following in my WXS:
Fragment
UI Id=MGALFAUI
TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
Where's the 'cmd.exe' in that command?
Kalvagadda, SivaKrishna (GMIT-TASS) [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/10/2008 02:43 PM
Please respond to
General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
To
General discussion for Windows Installer
Be careful, some text editors screw up the solution file. I know Textpad
for one does...
I personally use VS - I just close the solution, then use 'open file' to
open the sln file, clicking the down arrow on the Open button and
choosing 'text editor' in VS's open dialog.
Kelly
Simon
You need 'createAndRemoveOnUninstall' as the action for your key. I'm not
sure what the attribute is and I don't have a WiX project open right now,
but I'm sure somebody else will chime in or you can figure it out
yourself...
Kelly
Alex Ivanoff [EMAIL PROTECTED]
Sent by: [EMAIL
?
Thanks,
Kelly Leahy
**
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted
Is there a way to identify whether netfx 3.0 SP1 is installed using
WixNetFxExtension, or only whether the RTM is installed?
Our application requires 3.0 SP1 or higher, but it doesn't require 3.5.
Thanks,
Kelly
help us
with our installers.
Kelly
Friedrich Dominicus [EMAIL PROTECTED]
05/28/2008 11:13 PM
To
Kelly Leahy [EMAIL PROTECTED]
cc
Neil Enns [EMAIL PROTECTED], wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Subject
Re: [WiX-users
Did you add a FeatureRef in your feature tree for this feature?
You have to include something from the fragment in your wxs or else it
won't get linked in.
Kelly
alan sinclair [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
05/29/2008 05:12 PM
To
WiX-users@lists.sourceforge.net
cc
Subject
Christopher,
Perhaps you could put together your list of 'best case' requirements for a
bootstrapper? It seems like building one isn't going to be that
difficult, but it also seems that the project is starved of good
requirements and direction around the bootstrapper.
Once there's a good
,
but the stupid tool won't let me do it'.
Kelly
Friedrich Dominicus [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
05/28/2008 12:05 AM
To
Kelly Leahy [EMAIL PROTECTED]
cc
Neil Enns [EMAIL PROTECTED],
[EMAIL PROTECTED]
[EMAIL PROTECTED],
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
Hehehe... just got done blogging about how to make a single-.EXE package
with .NET yesterday. The methodology I used can be used for both managed
and unmanaged projects (although it's admittedly much easier for managed
projects). It may help a little, though its not exactly what you're
To
Neil Enns [EMAIL PROTECTED]
cc
[EMAIL PROTECTED]
[EMAIL PROTECTED], Kelly Leahy
[EMAIL PROTECTED], wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] Create EXE wrapper around my MSI?
I was finally able to wrap my MSI with an EXE installer and run my
That was my understanding as well (i.e. localservice is the best, but
often useless because it's not powerful enough, networkservice is better
but still secure, localsystem is like leaving the front door of fort knox
unlocked).
It's true that an account that is completely customized to the
Wow... That's got to be the wierdest 'feature' I've ever seen.
Christopher Painter [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
05/23/2008 11:03 AM
To
Neil Enns [EMAIL PROTECTED], wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net
cc
Subject
Re: [WiX-users] Why isn't my
dumb question (maybe).
Is script null upon entry into the loop you gave?
It can't be as far as I know for the += operator to work.
Kelly
Christopher Karper [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
05/21/2008 12:38 PM
To
Christopher Painter [EMAIL PROTECTED]
cc
01:21 PM
To
Jason Ginchereau [EMAIL PROTECTED], Christopher Karper
[EMAIL PROTECTED], Kelly Leahy [EMAIL PROTECTED]
cc
[EMAIL PROTECTED]
[EMAIL PROTECTED],
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] DTF Stream Operations Issue
Database db = new
I think you need to look at the IsPriveleged property in MSI for your
check, and theres some way to make the installer require elevation in the
manifest file. I'm not sure how to do that though. You might search for
UAC manifest MSI or something like that.
Kelly
Colin Bleckner [EMAIL
for
that?
Kelly
Rob Mensching [EMAIL PROTECTED]
05/15/2008 08:54 PM
To
Kelly Leahy [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Subject
RE: [WiX-users] really slow using pyro
“safe” is one way to look at it. “correct
I guess the list doesn't like attachments. Any recommendations of where
to put them?
- Forwarded by Kelly Leahy/SEAT/MILLIMAN on 05/15/2008 09:23 AM -
Kelly Leahy
(Seattle)
05/15/2008 09:14 AM
To
Rob Mensching [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net wix-users
What's the difference between wix3_x64.msi and wix3.msi on the weekly
releases?
Is the x64 for targeting x64, running WiX on x64, or what?
Does it not include the x86 versions of CAs?
Just curious,
Kelly
**
To
Kelly Leahy [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] really slow using pyro
One more question: can you give me an idea of the time spent building MSI
vs. building MSP? Basically, I’m looking for a bit more details about
You need a bootstrapper for this. You won't be able to nest the
installers in any way that works.
Neil Enns [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
05/15/2008 04:45 PM
To
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
cc
Subject
[WiX-users] Installing .NET 3.5 redist?
OK... I've been installing the x86 version. If I'm running on the x64 OS
(Vista x64) should I be using the x64 version?
Kelly
Rob Mensching [EMAIL PROTECTED]
05/15/2008 08:32 PM
To
Kelly Leahy [EMAIL PROTECTED], wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net
cc
Subject
The page at:
http://wix.sourceforge.net/manual-wix2/preprocessor.htm
Seems to indicate that ?if xxx Or yyy? will evaluate to to true if xxx
is defined or if yyy is defined, but that it will evaluate to false if
both are undefined.
However, when I try to use this with undefined vars, I get an
to
incrementally build our installer (i.e. build a wixlib or a msm for the
content that just gets merged (hopefully quickly) into the output msi)?
Is this likely to improve things, or is it more likely that this will take
just as long to build as the other process?
Thanks,
Kelly Leahy
time, and plenty of time to 'eat our own dog food'.
If you have any recommendations of folks that could help with this, please
contact me with details.
Thanks,
Kelly Leahy
Milliman, Inc.
**
This communication
This vbs is meant to be run by windows installer. You can't just double
click it - windows installer defines 'Property' as a member of it's global
object. This is a feature of windows script hosts - they can register an
object to act as the set of 'globals' for the hosted script.
Kelly
See the CustomAction element in WiX. I don't remember the exact syntax.
You'll also need to add that custom action to one of the execute
sequences.
Kelly
Kai Lee [EMAIL PROTECTED]
05/05/2008 09:10 AM
To
Kelly Leahy [EMAIL PROTECTED]
cc
[EMAIL PROTECTED] [EMAIL PROTECTED],
wix-users
time, and plenty of time to 'eat our own dog food'.
If you have any recommendations of folks that could help with this, please
contact me with details.
Thanks,
Kelly Leahy
Milliman, Inc.
**
This communication
My bet is that it's using two MSIs and bootstrapping, maybe with a shared
'external' cab for less overhead in size.
Christopher Painter [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/04/2008 09:20 AM
To
Bob Arnson [EMAIL PROTECTED], SaiTeja [EMAIL PROTECTED]
cc
As Gabor said,
This reference is a reference to the way normal apps should retrieve the
value of that folder name, not the way that installers should retrieve it
- they should just use the MSI property. I'm not sure why that reference
is even made in the MSI documentation - it's confusing at
I would say that you're not going to have much luck in this endeavor.
Personally, I don't care which way its done, and I prefer the 'reply at
top' since I already know what they're replying to most of the time and I
have having to 'look for' the reply.
That said, if you try to impose your
Or it _does_ cause them to get copied over to the DLL1 side-by-side
folder, but then my program can't find DLL1 anymore for reasons I
can't figure out.
Uhh... I think I can explain this one. Consider the following case:
DLL1 in folder not in path
DLL2 in folder not in path
DLL1 loads DLL2
into DLL1's WinSxS folder unless they're included in
the assembly manifest. Despite the fact they're part of DLL1's
Component block in Wix.
On Dec 6, 2007 4:10 PM, Kelly Leahy [EMAIL PROTECTED] wrote:
Or it _does_ cause them to get copied over to the DLL1 side-by-side
folder, but then my
I don't believe what you want is achievable with windows installer, but
I'm not an expert...
I think what you could do is make each version a feature in windows
installer terminology, and require installations to always be done via the
most recent install package.
You could then use 'major'
This seems to imply it will work. Not sure though, since it doesn't seem
to be documented:
http://www.installsite.org/pages/en/isnews/200110/index.htm
Chad Petersen [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/29/2007 10:33 AM
To
X.Y. D [EMAIL PROTECTED],
I don't know if this will help you or not, but this seems like it might be
helpful in some of these cases:
http://download.microsoft.com/download/5/6/a/56a0ed11-e073-42f9-932b-38acd478f46d/WindowsVistaUACDevReqs.doc
Gonzalo Diethelm [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/29/2007
I dont' think windows even has such a feature, so I'd be surprised if MSI
does.
I think that's the whole reason why iisreset is a program and they don't
just rely on people having to do net start / net stop commands.
By the way, if you know the dependencies, you could just do net start and
I don't know if it's possible to produce exactly the same MSI, but I think
your problem is related to automatically generated package codes or
product codes. If you want to be able to rebuild an MSI that acts exactly
the same as one that already went out the door (I think this is generally
a
Nope... As far as I know, NOTHING will work in that scenario. AFAIK,
there's no way to handle this properly - you pretty much want to require
that users either only can install as Everyone, or only can install as
Just Me. Personally, I think Just Me is silly and can't come up with
any good
0x8007006E = -2147024786 = The system cannot open the file or device
specified. (from WinXP SP2)
My guess is that it's a path issue. Perhaps there's some way you can
figure out what your working path is at that point? I think it's probably
the path to the MSI, but I'm not sure.
Kelly
si
I think the generally preferred way of handling this is one of:
(1) provide a list of SQL server instances on the machine and allow the
user to choose which instance to install to
(2) default to [COMPUTERNAME] as the instance name, and allow the user to
override the choice on the command line of
Well, I couldn't find a bug report either, but here's somebody talking
about a fix they used (they used the tool from Mono with minor
modifications)
http://tondrej.blogspot.com/
Kelly
Shawn Edwards [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/07/2007 08:55 PM
Please respond to
[EMAIL
How about the last lines in this article:
http://msdn2.microsoft.com/en-us/library/aa387764.aspx
See where it says:
Note When signing an executable file that is larger than approximately
300 megabytes, you should use catalog signing with the MakeCat tool rather
than use the SignTool tool.
Let me guess, you build with VS2005 SP1, right?
You need to deploy the SP1 version of the VCRT components, or you need to
statically link to the runtime in your CA dll (better choice).
Kelly
Jaguar 36 [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/05/2007 10:03 AM
To
wix
To
Eric Baudouin [EMAIL PROTECTED], Kelly Leahy
[EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Subject
RE: [WiX-users] Font definition and WXL
I actually rewrote the code for the last test. If you look
Marc, I concur with Brian, but make sure you have your AppSearch sequenced
somewhere before your RemoveExistingProducts in this case, or else MSI
will remove the existing version before you get a chance to search the
registry for the item. BTW, if you have already released 1.0 and you
can't
I don't know anything about using MSI to install virtual directories, but
I think the solution is to put your 'shared' parent directory in a
component that is used by all of your applications, using the same
ComponentGuid. Then, only the 'first' application installed will add the
directory,
It doesn't look to me like there's a way to do this, but I don't know
anything about WiX's support for IIS.
Hopefully somebody else will recommend.
Kelly
Rolando [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/01/2007 04:00 PM
To
Kelly Leahy [EMAIL PROTECTED]
cc
[EMAIL PROTECTED], wix
Don't you want $(loc.BannerTextStyle_Size) not
!(loc.BannerTextStyle_Size)?
Kelly
Eric Baudouin [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/01/2007 04:17 PM
To
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
cc
Paul Houldridge [EMAIL PROTECTED]
Subject
[WiX-users] Font
the variable is defined.
NMAKE : fatal error U1077: 'C:\DRS_SYNC_1\Tools\wix3\light.exe' : return
code '0x66'
NMAKE : fatal error U1077: 'C:\DRS_SYNC_1\Tools\wix3\light.exe' : return
code '0x66'
Stop.
From: Kelly Leahy [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 01, 2007 4:31 PM
To: Eric
Would adding 'Or Installed' to the condition work as well? Wouldn't it
then remove the file if it's there, and leave it if it isn't?
Kelly
Anthony Wieser [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/30/2007 08:00 AM
To
wix-users@lists.sourceforge.net
cc
Subject
Re: [WiX-users]
Subject
Re: [WiX-users] Maintenance modes SOLVED!
It's not my file. I'm modifying a registry entry based on whether I find
a file in the system folder.
Anthony Wieser
Wieser Software Ltd
- Original Message -
From: Kelly Leahy
To: Anthony Wieser
Cc: wix-users
The problem is the sequencing. By the time InstallFinalize has happened,
the install is already committed, so you can't roll back the install of
version 2, at least if I'm understanding it correctly. You probably want
your RemoveExistingProducts to be somewhere earlier in the sequence, so
).
Is the NETFRAMEWORK20 variable defined for machines that have ONLY .NET
3.0, or ONLY .NET 3.5?
If not, what's the recommended best practice for requiring anything that
can run 2.0 code, in other words, .NET 2.0 or higher?
Thanks,
Kelly Leahy
Milliman, Inc
, but I'm just curious.
Kelly
Matt Hoover (VSNC) [EMAIL PROTECTED]
10/25/2007 03:37 PM
To
Kelly Leahy [EMAIL PROTECTED], wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net
cc
Subject
RE: [WiX-users] detecting .net 2.0
It is not possible to have only .Net 3.0 or only .Net 3.5
Is anything in Wix 3.0 documented?
Sorry. I just couldn't resist.
Rob Mensching [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/23/2007 03:11 PM
To
'Rob Mensching' [EMAIL PROTECTED], 'Adam Majer' [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] wixout file
Yep... I kinda forgot the smiley in my email :)
So where is the 'command lines and the tools to use' documentation
located, precisely?
Kelly
Rob Mensching [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/24/2007 09:05 AM
To
'Kelly Leahy' [EMAIL PROTECTED]
cc
[EMAIL PROTECTED], wix-users
What about using 'two' wixout files - one for the cab and one for the xml?
In other words, an ancillary file that stores the cab.
Kelly
Rob Mensching [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/23/2007 03:05 PM
To
'Adam Majer' [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net
Rob Mensching [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/23/2007 03:35 PM
To
'Kelly Leahy' [EMAIL PROTECTED]
cc
[EMAIL PROTECTED], wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] wixout file format
Then there would be two files… which would have to be remembered to be
copied
Jason,
Would you happen to be checking the path on an existing command line
window, or have you opened a new one? The path of existing command line
windows does not change when the system is updated (there isn't really any
good way to do this, since the user could have changed the path
Yep... definitely shouldn't be moving built-in files like msbuild.exe.
Lots of bad things can happen as most of those sorts of tools assume they
are in a particular location when you're using them.
Better to qualify your path to the file or use the windows path to get a
reference to it via
what about #xD and #xA... Do those work?
Kelly
Stefan Pavlik [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/17/2007 10:39 PM
To
Nitin Chaudhari [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] How to add newline in Condition message
Hi
WiX does not
Why zip files? Why not just use MSI's compression?
Craig0ss [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/04/2007 12:53 AM
To
wix-users@lists.sourceforge.net
cc
Subject
[WiX-users] Zip files and Wix Can It Be Done
Hi Guys/Girls
I need to ship files wit my installer, these files
To
'Kelly Leahy'
[EMAIL PROTECTED]
10/04/2007 08:05 cc
AM
To
Kelly Leahy [EMAIL PROTECTED]
cc
[EMAIL PROTECTED], Hongping Lim
[EMAIL PROTECTED], wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] How to check processor architecture
On 4 Oct 2007, at 02:42, Kelly Leahy wrote:
Oh... If you're looking for OS
To set the default value of the combo box, do a custom action to set the
property underlying the combobox to the default value you want after
filling the combobox.
something like:
CustomAction Id=setProperty Property=PROPERTYNAME Value=value/
I think.
Then make sure you sequence it after
You can't build one package for x64 and x86. However, if all you're doing
is putting stuff in the Win32 normal places (not messing with x64 registry
or file system), you should be able to check for the existence of Intel or
Intel64 properties. I think windows installer sets these as
Oh... If you're looking for OS = x64 or x86, rather than processor x64
vs. x86, you'll probably want to look at VersionNT64 (also requires
version 4.0 of MSI).
Kelly Leahy [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/03/2007 06:39 PM
To
Kelly Leahy [EMAIL PROTECTED]
cc
[EMAIL PROTECTED
Go to c:\program files\microsoft visual studio8\common7\tools (if you have
VS2005 installed) and run
errlookup.exe
put the number into the box and you'll see it change to: 0x80110404
you'll see the message: The object is already registered
So... not sure what that means in your case - I'm
Oops. Sorry Chris for the duplicate - I forgot to reply to all on the
first one.
Here's what I sent to Chris - others, tell me if this won't work, because
I may need this approach myself, later in my installer building process.
You could do custom actions that set another property based on
of course, with more than just the two actions.
However, I'm by no means an expert and haven't even tried compiling this,
so it's very possible I'm heading you down the wrong path.
Kelly
Chris Ridd [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
09/27/2007 10:09 AM
To
Kelly Leahy [EMAIL PROTECTED
Does Wix uninstall fonts that were installed by a Wix-based installer? It
seems like it doesn't.
I understand it's probably not a good idea to uninstall fonts, since
there's no refcounting behavior for them. I just want to make sure it
really doesn't uninstall them and I'm not just seeing
but not remove it? I'm assuming it isn't. This is the behavior I want,
however, since my application must work with several versions installed
side-by-side, and I don't want someone removing an older version to cause
the newer versions to lose the fonts.
Kelly
Kelly Leahy [EMAIL PROTECTED
from the treeview, or
will it always be shown there?
Kelly
Bob Arnson [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
09/24/2007 11:12 PM
To
Kelly Leahy [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] How to hide features based on CD-KEY
Kelly Leahy wrote
95 matches
Mail list logo
