Leave what you have in the current fragment, but add a ComponentGroup that
contains a ComponentRef for each component. Then add a ComponentGroupRef to
the different Features.
-Brian Simoneau
-Original Message-
From: Jakub Gwóźdź [mailto:gwozd...@rpg.pl]
Sent: Thursday, January 21
It is indeterminate. Either action may run first. If you need them to
be in a certain order, then schedule them relative to each other instead
of just relative to CostFinalize.
-Brian Simoneau
-Original Message-
From: Kevin Garman [mailto:gar...@scadaware.com]
Sent: Thursday, December
My company was using InstallShield before switching to WiX. I have
never used InstallAware, but the only advice I can give is to use WiX.
It's free and can do anything that the commercial products do, sometimes
better.
-Brian Simoneau
-Original Message-
From: Matt W
If you want a minor upgrade, you have to go with
* install msi with command REINSTALLMODE=vomus, not good for
normal users
You don't make the users do this themselves. Create a bootstrapper that
passes that argument when doing a minor upgrade.
-Brian Simoneau
-Original Me
No, in fact I just read your message there.
-Brian Simoneau
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Friday, May 22, 2009 1:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] wix-users archive on SourceForge
Does
You can set MSIRESTARTMANAGERCONTROL to Disable.
-Brian Simoneau
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: Tuesday, May 12, 2009 11:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Files in use
The difference
http://www.installsite.org/pages/en/msifaq/a/1042.htm
-Brian Simoneau
-Original Message-
From: Jan Bilek [mailto:bil...@gmail.com]
Sent: Thursday, April 23, 2009 2:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to disable/bypass FilesInUse dialog
Hello,
Is there
What are you using then to handle executable COM servers?
-Brian Simoneau
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, April 16, 2009 6:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Fails to register a
Check out the bottom of the tutorial pages. The tutorial was created by Gábor
DEÁK JAHN and not the WiX team itself. Any questions about the tutorial should
go to him.
-Brian Simoneau
-Original Message-
From: Louis elston [mailto:louels...@comcast.net]
Sent: Wednesday, March 25
Components can be marked Permanent. Any files in the component would
not be uninstalled.
-Brian Simoneau
-Original Message-
From: Hugo Vale [mailto:hugov...@gmail.com]
Sent: Thursday, March 12, 2009 1:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FW: Permanent xml tag
You can use the UILevel property.
http://msdn.microsoft.com/en-us/library/aa372096(VS.85).aspx
-Brian Simoneau
-Original Message-
From: sandun css [mailto:sandun...@gmail.com]
Sent: Thursday, March 05, 2009 5:26 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Verify the
This is not possible with a Windows Installer tree control. You will need to
write your own.
-Brian Simoneau
-Original Message-
From: Corry, Davidson [mailto:davidson.co...@sage.com]
Sent: Friday, January 23, 2009 1:47 PM
To: General discussion for Windows Installer XML toolset
Try WindowFolder and SystemFolder.
-Brian Simoneau
-Original Message-
From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellteam.com]
Sent: Tuesday, December 30, 2008 2:29 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] A few questions
Thanks for the info! My
Add the batch file as a Binary and run the custom action before
InstallFiles.
-Brian Simoneau
-Original Message-
From: Yu, Brian [mailto:[EMAIL PROTECTED]
Sent: Monday, November 24, 2008 8:04 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] backuponinstall
Hi there
I am
If you own the code for tools.dll, you can change it to a library and
link the library in CustomActions.dll. Otherwise, you will have to
extract tools.dll onto the system before using it. There is no built-in
way to do this.
-Brian Simoneau
-Original Message-
From: Oren Mazor [mailto
What version did WiX start using smart cabbing? Has it been there all
along?
-Brian Simoneau
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Monday, November 03, 2008 11:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
Run your custom actions to set the properties in the
InstallExecuteSequence as well. Your installer may not run with the UI
anyways.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Rerick
Sent: Thursday, September 04, 2008 6:29 PM
I think it's the Error Dialog.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bernd
Adler
Sent: Monday, September 01, 2008 9:38 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ScheduleReboot Message
Hi,
Which Dial
ation. Instead, you can set your installer to a system component
and then write your own ARP entry.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nilkund
Aseef
Sent: Thursday, August 21, 2008 1:53 PM
To: wix-users@lists.sourceforge.net
Subject:
If that Property element is copied exactly, then there is the problem.
You are setting INSTALLERROR to Value="0". Change it to
0
Or
To set INSTALLERROR to 0.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Yuval
David
Sent
This has been answered on the mailing list before. Search for "Removing
Install to Run From Network Feature Option". This happens when a
feature only has sub-features and not components.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
are not evaluated and the default value is always used.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Friedrich
Dominicus
Sent: Friday, June 13, 2008 1:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX
Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
PROP1 exists. Something like
PROP1
You can do the same thing for PROP2 or set PROP2 as the default value of
ANOTHER_PROP since it is the else case.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto
After attribute is also the correct way to sequence actions.
-Brian Simoneau
From: Natxo Mateos [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 12, 2008 10:42 AM
To: Brian Simoneau
Subject: Re: [WiX-users] using one property to set an
Steps 1 and 3 both happen during the AppSearch action. There's no way
to break them apart and do MyAssign in the middle. You could do step 3
in a custom action after MyAssign.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Natxo
M
You can use the OriginalDatabase property.
-Brian Simoneau
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bir, Steve
Sent: Friday, May 02, 2008 3:09 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How
Deferred custom actions must be scheduled between InstallInitialize and
InstallFinalize.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, April 04, 2008 2:24 PM
To: Bob Arnson
Cc: wix-users
Look at the CompressionLevel attribute of the Media element.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Koloszar
Jozsef
Sent: Thursday, April 03, 2008 3:11 AM
To: Bob Arnson
Cc: WiX-users@lists.sourceforge.net
Subject: [WiX-users
I have also gotten crashes in the latest version of Orca when trying to
view patches. I ended up going back to an earlier version of Orca
(2.0.3790) which is more stable.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of LindseyLeu
Sent
I tried installing to a different drive. The other drive shows 68 MB
required, but there is still 91 MB required shown on the C drive. Is
there a way to redirect what temporary space Windows Installer uses?
-Brian Simoneau
From: Bob Arnson [mailto
required to handle rollback?
-Brian Simoneau
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 04, 2007 2:52 PM
To: Brian Simoneau
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Disk Usage
To get the second option to work, save the installation directory in the
registry when you install v1.0. Then when performing a major upgrade,
have v1.1 search the registry for the installation directory and use it.
-Brian Simoneau
From: [EMAIL
Where does the disk usage dialog get the values to put into the table?
The selection tree in the custom setup dialog indicates that the install
requires 68 MB, but in the disk usage dialog it says that 159 MB are
required on the drive. I would expect these values to be the same.
Brian Simoneau
The $ must be outside of the parentheses.
$(var.HelpSourceFolder) instead of ($var.HelpSourceFolder)
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of hina1703
Sent: Thursday, October 11, 2007 2:47 PM
To: wix-users@lists.sourceforge.net
How are the Directory elements defined? If the Directory element for
ANOTHERDIR is under the Directory element for INSTALLDIR, then changing
INSTALLDIR is expected to change ANOTHERDIR as well.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
The installer extracts the dll to the temporary location in order to
call the custom action and then deletes the temp file. The actual error
is in calling the custom action or in the custom action itself.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
You should read lesson 3 of the WiX tutorial
http://www.tramontana.co.hu/wix/lesson3.php
Look for how to set CustomActionData for your deferred actions.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of md5hans
Sent: Monday, October 01
The best way to leave a component is to give it a GUID but mark the
component as Permanent.
-Brian Simoneau
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kelly
Leahy
Sent: Wednesday, September 26, 2007 9:54 PM
To: Kelly
We use a bootstrapper that we wrote ourselves, but if you search this
list for "bootstrapper" you should find recommendations from others.
-Brian Simoneau
-Original Message-
From: Anton Filippov [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 20, 2007 12:18 AM
To: Brian S
You need a bootstrapper that can detect whether the app is installed.
If it is not installed, then run it normally. If it is installed, then
add the reinstall command line options.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anton
If you cancel the uninstall before the custom action is run, then there
is no problem. If you cancel after the custom action is run, then you
will need a rollback custom action to undo what the first custom action
did.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto
Well, the log mentions UninstallOldXYZ but the .wxs file has
UninstallOldBPM as the name of the action. Make sure any old versions
of the msi have been uninstalled and that the one you are running is the
correct one.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto
The sequence of events can be changed in an installer. You can use Orca to see
the sequence of events for your particular msi file.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet
Sent: Wednesday, September 12, 2007 10
Try this in your condition
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of stian
Sent: Wednesday, August 29, 2007 8:57 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GDI+ MergeModule
Thanks, but still the same error
Properties are case-sensitive, so try REINSTALL in your condition.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig Ward
Sent: Tuesday, August 28, 2007 8:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] minor upgrade
For ifdef and ifndef, just use the name of the variable. So your
statement should look like
-Brian Simoneau
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sameeksha
Chepe
Sent: Friday, August 24, 2007 12:33 AM
To
That would imply a different issue. I would look for your custom action
in the log to see if it is being run.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tanikella,
Rajanikanth (SCR US)
Sent: Thursday, August 09, 2007 9:56 AM
To
If your custom action is sequenced after InstallFinalize, then it should
be immediate. The commit and deferred types can only be used between
InstallInitialize and InstallFinalize.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Just use HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Hardware
Profiles\Current.
-Brian Simoneau
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stanislav
Martinek
Sent: Monday, August 06, 2007 11:08 AM
To: wix-users
You could write a permanent registry entry containing the path that the
user selected, then read the registry entry when the install is run
again to find out where it was installed before.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Use the ARPSYSTEMCOMPONENT property.
http://msdn2.microsoft.com/en-us/library/aa367750.aspx
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ward, Mike
(MED US)
Sent: Monday, July 23, 2007 1:59 PM
To: wix
You don't need to use square brackets in the condition because
properties are automatically resolved.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig Ward
Sent: Tuesday, July 17, 2007 9:24 AM
To: wix-users@lists.sourceforg
TE_LOCAL.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lawrence
Sent: Tuesday, July 17, 2007 2:55 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Feature installation condition
Hi all.
Forgive me if this has been covered bef
Try not setting REINSTALL and REINSTALLMODE. Those should only be
necessary for minor updates, but you are trying to do a major update.
-Brian Simoneau
-Original Message-
From: Nitin [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 12, 2007 11:49 AM
To
Versions 0.3.0 and 0.4.0 must have the same UpgradeCode but different
ProductCodes. If you are seeing maintenance mode, then they probably
have the same ProductCode.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nitin
Try instead.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Afshin
Sepehri
Sent: Monday, June 25, 2007 1:51 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Checking if an enivronment
Please include wix-users when you send messages.
Usually a property is used in WiX by surrounding it with square
brackets. So you would use [ComputerName].
-Brian Simoneau
-Original Message-
From: X.Y. D [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 14, 2007
Use the ComputerName property.
http://msdn2.microsoft.com/en-us/library/aa368009.aspx
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of X.Y. D
Sent: Thursday, June 14, 2007 9:53 AM
To: wix-users
Why doesn't RemoveFile work? Did you set On="install"?
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew
Janulewicz
Sent: Tuesday, June 12, 2007 1:08 PM
To: wix-users@lists.
Your ifdef should look like
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Fischer
Sent: Thursday, June 07, 2007 2:44 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Define
I am not using the latest version of WiX 2.0, so I am not sure where
else Preselected might be currently used. Making your own copy of
ProgressDlg.wxs should work, but I wonder if the condition that is being
used in the WiX ProgressDlg.wxs is not correct.
-Brian Simoneau
-Original
I think using /x to indicate uninstall will set REMOVE=ALL.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Charles
Wan-Calo
Sent: Friday, June 01, 2007 2:14 PM
To: wix-users@lists.sourceforge.net
Is there a way to set the permissions of a shortcut in WiX? I can see
that the Permission element can be used on a File, but is there
something available for a Shortcut?
Brian Simoneau
Software Developer
Freedom Scientific
Add Execute="deferred" to your CustomAction element.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 30, 2007 2:34 PM
To: Brian Simoneau
Subject: Re: [WiX-users] Help!!! Can&#x
Your Custom Action has to be deferred. If it is immediate (the
default), then it is run before the exe gets installed onto the system.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
mikebartlett
Sent: Wednesday, May 30, 2007 12:57 PM
To
That should be possible.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu
(Volt)
Sent: Tuesday, May 22, 2007 7:52 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Can I put
We are using a custom action to make a directory hidden. I think there
is only built-in support to make files hidden.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of ccitt
Sent: Tuesday, May 22, 2007 2:23 PM
To: wix-users
Yes, you can't define files to install in a Binary element. A binary
can be used by the installer but is not installed on the system. You
must be File elements as part of a Component.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Beha
You need to define File elements under each of those Components.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of ccitt
Sent: Tuesday, May 22, 2007 1:05 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installer not placing any
Are you sure that it was doing a minor upgrade? A major upgrade doesn't
require command line arguments, but the product code and version have to
be changed, the upgrade code has to stay the same, and the Upgrade table
has to be authored appropriately.
-Brian Simoneau
-Ori
I think this is wishful thinking. A minor upgrade is going to require
command line parameters for msiexec.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rory Clark
Sent: Thursday, May 17, 2007 12:18 PM
Building in the WiX help. You can try reading that as
well.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erich
Buhler
Sent: Thursday, May 17, 2007 10:13 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error when changing the
es will be
uncompressed.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erich
Buhler
Sent: Thursday, May 17, 2007 9:32 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error when changing the compression
Hi, thanks again!
That'
It should be set in the user interface. Look for "SetInstallLevel".
-Brian Simoneau
-Original Message-
From: Simon Topley [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 17, 2007 9:25 AM
To: Brian Simoneau; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Default fea
That command line doesn't look correct. Why is the "msi" after the -l
option? Is the log getting created?
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erich
Buhler
Sent: Thursday, May 17, 2007 9:12 A
components themselves.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Venkatesh
Sent: Thursday, May 17, 2007 8:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Problem with condition
The default state of a feature is based on the Feature Level. If the
Feature's Level is greater than the INSTALLLEVEL property, then the
feature is not selected by default.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon
T
Creating an uncompressed version of an installer is not a requirement
for creating a patch. You can perform an admin install of your package
and then build the patch using the admin install image.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
In the General Configuration Properties, you also need to set Use of MFC
to Use MFC in a Static Library. That should get rid of the dependency
and increase the size of the dll.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
A simple call to launch a message box would be
MessageBox(NULL, _T("Custom action"), _T("Attach"), MB_OK);
Note that this is not the correct way to show a message box to a user
during installation, but for temporary debugging works fine.
-Brian Simoneau
-
launching the custom action, there may be a missing
dependency.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 4:51 PM
To: Brian Simoneau; WiX-users@lists.sourceforge.net
Subject
_T is a macro defined in tchar.h. I believe this was included in
earlier Visual Studios because my custom actions were originally written
in VS2003. It looks like __out and others are defined in sal.h.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto
That code looks the same as what I am using except that I have _T()
around my strings. Are you running your custom action immediate or
deferred?
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007
You have to call WcaInitialize in your method before you can call
WcaLog. You also need to call WcaFinalize before you exit the method.
So your last line could look something like:
return WcaFinalize(ERROR_SUCCESS);
-Brian Simoneau
-Original Message-
From: [EMAIL
If you are writing a C++ custom action, then the WcaLog function in
wcautil will write to the install log or show you how to do it yourself.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent
Under the Package element, you should have Compressed='yes' instead of
'no'.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of dave_c
Sent: Tuesday, February 20, 2007 11:37 AM
To: wix-users@lists.sourceforge.net
Subjec
Based on the error message it looks like tallow does not support your
wsc file. You may want to take a look at heat, which is part of WiX 3.0
and may do more than tallow. Otherwise, you will have to determine the
registry entries yourself.
-Brian Simoneau
-Original Message-
From
If the file is called file.dll and it is in the current directory, then
tallow -s file.dll
should work. You can use -nologo to skip printing the copyright
information at the beginning.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Using self registration in an installer is not recommended. See the
remarks for the SelfReg table.
http://msdn2.microsoft.com/en-gb/library/aa371608.aspx
You can instead use tallow to extract the registry keys that are
installed by SelfReg and add those registry keys to your installer.
-Brian
I think that !FeatureName is the current state of the feature and
&FeatureName is the action to be performed.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Hamflett
Sent: Tuesday, February 06, 2007 4:30 AM
To: wix-u
Title: Message
Rollback actions must be sequenced before the action that could cause the
failure. It looks like you have the rollbacks actions defined after the
install actions.
-Brian
Simoneau
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Try [ProductCode] instead.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of coolfishx
Sent: Tuesday, August 22, 2006 8:12 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Write Autogenerated Product Id in an Ini File
The Product ID is stored in the property ProductID. The Value attribute
should be [ProductID].
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of coolfishx
Sent: Tuesday, August 22, 2006 4:53 AM
To: wix-users@lists.sourceforge.net
Subject
Title: Message
Do you
mean that the system menu font is not overridable using Windows
Installer or that there are no Windows APIs for changing it
directly?
-Brian
Simoneau
-Original Message-From: Bob Arnson
[mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 11:06
size.
Thanks,
Brian Simoneau
Software Developer
Freedom Scientific
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Monday, August 07, 2006 5:08 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom actions
I made that change, that you suggested and now I get this error in the
The Property attribute should contain the full path of the executable
and the ExeCommand attribute should only have the command line
parameters. Try
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Monday, August 07, 2006
When you don't have the dummy file and shortcut, does your msi have
InstallFiles and CreateShortcuts in the InstallExecuteSequence? If not,
then rather than adding a dummy file and shortcut, you can add those
actions directly to your wxs.
-Brian Simoneau
-Original Message-
From: [
The syntax for using the localization string should be
$(loc.UninstallAppShortcut). I'm guessing that
!(loc.UninstallAppShortcut) is evaluating to the null value.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laurent
Courbet
Title: Message
Try
Id="SystemFolder" Name="System">
The
SystemFolder property will automatically resolve to system32.
-Brian
Simoneau
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sherwood
HuSent: Friday, J
1 - 100 of 108 matches
Mail list logo
