ath.
Better yet, replace cmd \c with %COMSPEC% \c if the function will expand
environment variables.
-Original Message-
From: David Amey [mailto:da...@creative-engine.co.uk]
Sent: 20 June 2011 14:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] logging
: +44 (0)1483 799111
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: 15 June 2011 15:54
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] logging
Hi David,
I am not expert in candle and light but I believe that redirect
_FOLDER,@SW_MAXIMIZE)
Martin Kulov
-----Original Message-
From: David Amey [mailto:da...@creative-engine.co.uk]
Sent: Wednesday, June 15, 2011 12:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] logging
Hi Dave,
Thank you for this link.
I have been try
bly grateful.
Thanks!
David Amey
The Creative Engine Ltd
Almac House, Church Lane, Bisley, Surrey, GU24 9DR
T: +44 (0)1483 799200 F: +44 (0)1483 799111
-Original Message-
From: Dave Andersen [mailto:d.ander...@gmail.com]
Sent: 14 June 2011 19:28
To: wix-users@lists.sourceforge.net
Sub
Something like this may help:
http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scripts/
David Amey wrote:
>
> Hello All
>
> Can someone please explain how I can turn logging on during the candle and
> light calls, as I have errors that I need to correct.
> I am automating
, 2010 7:52 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging while uninstalling from Control Panel
On 8/6/2010 3:13 PM, Ivo Beltchev wrote:
> I think you can edit the registry (via custom action or another way)
> to set WindowsInstaller to 0, and change UninstallStr
On 8/6/2010 3:13 PM, Ivo Beltchev wrote:
> I think you can edit the registry (via custom action or another way) to
> set WindowsInstaller to 0, and change UninstallString to "MsiExec.exe /x
> {blah} /l*v C:\q.txt".
>
No, ARP ignores that string.
--
sig://boB
http://joyofsetup.com/
-
lease consider the environment before printing this e-mail
>
>
> -Original Message-
> From: Sai Kodi [mailto:saik...@hotmail.com]
> Sent: Friday, August 06, 2010 9:50 AM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users]
di [mailto:saik...@hotmail.com]
Sent: Friday, August 06, 2010 9:50 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Logging while uninstalling from Control Panel
Hi Pally,
That's not what I am looking for. I have already done that search and I
With MSI 4.0 and above, you can use the MsiLogging property.
-Original Message-
From: Sai Kodi [mailto:saik...@hotmail.com]
Sent: Friday, August 06, 2010 9:50 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Logging while uninstalling fr
com]
Sent: Friday, August 06, 2010 4:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging while uninstalling from Control Panel
http://lmgtfy.com/?q=how+to+enable+windows+installer+logging
Palbinder Sandher
Software Deployment & IT Administrator
T: +
http://lmgtfy.com/?q=how+to+enable+windows+installer+logging
Palbinder Sandher
Software Deployment & IT Administrator
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. Registered in Scotla
Why not? You can use Session.Log() in deferred CA as well.
-- Yan
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: Tuesday, July 20, 2010 13:05
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Logging in deferred CA
Hello!
Thanks for the response. That appears to have been the issue.
-Original Message-
From: Jeremy Farrell [mailto:jfarr...@pillardata.com]
Sent: Monday, July 19, 2010 5:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging Error
Perhaps Windows
Perhaps Windows path separators (\) in the paths?
> From: Thode, Katelyn [mailto:katelyn.th...@guidancesoftware.com]
>
> I am attempting to log the installation of a package I
> created. When I run the following command line:
>
> msiexec.exe /I "C:/comp/code/libdbg/tfuInstaller.msi" /l*v
> "
nt: Friday, July 09, 2010 9:33 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Logging information
>
> Hi,
> Thanks for reply. Actually I want to register our com exe. We are using heat
> to create the .wxs file. It contains the information about class an
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging information
Hi
Windows Installer doesn't support logging the console output of command you
execute through a custom action.
Consider using CAQuietExec to execute your custom action. That will do two
t
Windows Installer doesn't support logging the console output of command you
execute through a custom action.
Consider using CAQuietExec to execute your custom action. That will do two
things for you:
1.) Hide the command prompt window that shows up for console applications.
2.) Capture your cons
.
Subject: Re: [WiX-users] Logging from XML file?
Sorry, I meant my Product.wxs (or any other wix xml source). Generally I
would just like to have something printed to the log if I did:
msiexec /i myinstaller.msi /l* install.log
I would like to do something like this:
Thanks,
slide
On Wed
...@gmail.com]
Sent: Wednesday, December 02, 2009 6:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging from XML file?
Sorry, I meant my Product.wxs (or any other wix xml source). Generally I
would just like to have something printed to the
Check out the MsiLogging property in the MSI SDK.
On Wed, Dec 2, 2009 at 6:09 PM, Slide wrote:
> Sorry, I meant my Product.wxs (or any other wix xml source). Generally I
> would just like to have something printed to the log if I did:
>
> msiexec /i myinstaller.msi /l* install.log
>
> I would li
Sorry, I meant my Product.wxs (or any other wix xml source). Generally I
would just like to have something printed to the log if I did:
msiexec /i myinstaller.msi /l* install.log
I would like to do something like this:
Thanks,
slide
On Wed, Dec 2, 2009 at 6:44 PM, Blair wrote:
> Whic
Which XML file are you referring to, and what do you want to log that comes
from that file?
Off the top of my head I don't know of anything specific, but the answers to
these questions will go a long way to getting you an answer.
-Original Message-
From: Slide [mailto:slide.o@gmail.co
ually do
> > it
> > feels like it skips the candle and light process. It does not build
> > anything
> > and no log file is created... Maybe something to do with ">" char?? Or
> what
> > do you think?
> > Thank you in advance!
> > Peter
&g
ter
>
> 2008/10/6 Phil Sayers <[EMAIL PROTECTED]>
>
> > anyone else received this message almost 10 times today?
> >
> > -Original Message-
> > From: Peter Vestergaard [mailto:[EMAIL PROTECTED]
> > Sent: Monday, October 06, 2008 6:47 AM
> > To:
build anything
and no log file is created... Maybe something to do with ">" char?? Or what
do you think?
Thank you in advance!
Peter
2008/10/6 Phil Sayers <[EMAIL PROTECTED]>
> anyone else received this message almost 10 times today?
>
> -----Original Message-----
>
anyone else received this message almost 10 times today?
-Original Message-
From: Peter Vestergaard [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2008 6:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging
I am using the command line
You haven't actually called light on your command line. Have you registered
the .wixobj file
extension with light or something?
Rob
Peter Vestergaard wrote:
> Thanks for your assistance. It does however not work for me...
> my command is: "C:\Projects\...\WiXOutput.wixobj" -out
> "C:\Projects\
Thanks for your assistance. It does however not work for me...
my command is: "C:\Projects\...\WiXOutput.wixobj" -out
"C:\Projects\...\Installer.msi" -ext WixUIExtension -loc
"C:\Projects\...\Language.xml" 1>out.txt 2>err.txt
2008/10/6 Rob Hamflett <[EMAIL PROTECTED]>
> For one product my light c
For one product my light command is this:
light -nologo -sw1044 DBS.wixobj SN_COMMON_PATH.wixobj
Add_Common_Bin_To_Path.wixobj -loc
Common\CommonSettings\Common-E.wxl -loc English.wxl -out DBS.msi
You would then tag the redirection stuff on the end like this:
light -nologo -sw1044 DBS.wixobj SN_
I am using the command line
On Mon, Oct 6, 2008 at 12:38 PM, Simon Dahlbacka
<[EMAIL PROTECTED]>wrote:
> Or if you use votive (or othervise msbuild compatible project), you can use
> the normal msbuild logging mechanism
>
> http://msdn.microsoft.com/en-us/library/ms171470(VS.80).aspx
>
> /Sim
Or if you use votive (or othervise msbuild compatible project), you can use
the normal msbuild logging mechanism
http://msdn.microsoft.com/en-us/library/ms171470(VS.80).aspx
/Simon
On Mon, Oct 6, 2008 at 1:15 PM, Peter Vestergaard <[EMAIL PROTECTED]>wrote:
> Thanks for your reply.
> I can't get
Thanks for your reply.
I can't get this to work with light. Could you give me an examble of the
correct syntax?
-Peter
On Mon, Oct 6, 2008 at 10:45 AM, Rob Hamflett <[EMAIL PROTECTED]> wrote:
> There's the traditional method of redirecting the output:
> candle 1>stdout.txt 2>stderr.txt
>
> Rob
> If you're looking for a quick non-debugger method, property
> changes are still logged. It may be a hack, but calling
> MsiSetProperty(hMSI, _T("LOGME"), _T("...")) is effective.
Michael,
That's a nice workaround - I like it.
Cheers,
John
--
There's the traditional method of redirecting the output:
candle 1>stdout.txt 2>stderr.txt
Rob
>Peter Vestergaard wrote:
> Hi.
> Is there any way to log candle and light build errors and warnings to a text
> file?
> Best regards
> Peter
>
In article <[EMAIL PROTECTED]>,
"Michael Urman" <[EMAIL PROTECTED]> writes:
> If you're looking for a quick non-debugger method, property changes
> are still logged. It may be a hack, but calling MsiSetProperty(hMSI,
> _T("LOGME"), _T("...")) is effective.
Another option is to call OutputDe
On Thu, Oct 2, 2008 at 3:13 AM, John Hall
<[EMAIL PROTECTED]> wrote:
>> Yeah, Windows Installer doesn't let it work. Why? Some
>> message processing issue inside them. I think this is
>> documented in some small print somewhere.
>>
>> PS: Please don't shoot the messenger.
>
> Of course not. I
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
> Yeah, Windows Installer doesn't let it work. Why? Some
> message processing issue inside them. I think this is
> documented in some small print somewhere.
>
> PS: Please don't shoot the messenger.
Of course not. I had half guessed it was something like this anyway. I guess
it's a matter o
Yeah, Windows Installer doesn't let it work. Why? Some message processing
issue inside them. I think this is documented in some small print somewhere.
PS: Please don't shoot the messenger.
-Original Message-
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 200
[EMAIL PROTECTED] wrote:
As in /MD instead of /MT?
Other way. /MD[d] says to use the CRT DLL; /MT[d] says to statically
link the CRT.
--
sig://boB
http://bobs.org
-
This SF.net email is sponsored by DB2 Express
Downlo
odule.
Phil Wilson
From: Peterson, Joel [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 1:53 PM
To: Simon Dahlbacka; Wilson, Phil
Cc: WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
After installing Visual Studio 2005 SP1, the WinSxS Merge Modules
7 11:03 AM
To: Wilson, Phil
Cc: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
On 4/27/07, Wilson, Phil <[EMAIL PROTECTED]> wrote:
Ah, ok, the one in [ProgramFilesFolder]Microsoft Visual Studio
8\SDK\v2.0\BootStrapper\Packages\vcredist_x86 is
f a missing library or version incompatibility?
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 11:53 AM
To: Rowland, Chris
Cc: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
[EMAIL
2007 17:50
To: LEMIRE, JOHN; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
There is a tool out there called "depends.exe" that does this *and* provides
a spiffy tree that shows all the dependencies your code has. I use this
tool *all the time* to
On 4/27/07, Wilson, Phil <[EMAIL PROTECTED]> wrote:
Ah, ok, the one in [ProgramFilesFolder]Microsoft Visual Studio
8\SDK\v2.0\BootStrapper\Packages\vcredist_x86 is up to date with SP1.
yes, I should probably have mentioned that (as long as you pull it from a
machine that has been updated wi
EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: Friday, April 27, 2007 10:45 AM
To: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
I find it hard to believe they put a refresh up there on April 10th that
is not for SP1, but you
nt: Friday, April 27, 2007 9:58 AM
To: Wilson, Phil
Cc: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
On 4/27/07, Wilson, Phil <[EMAIL PROTECTED]> wrote:
As an easy test, install the VC support redist for VS 2005 on a
test system and see if yo
As in /MD instead of /MT?
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 12:08 PM
To: Rowland, Chris
Cc: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
[EMAIL PROTECTED
AIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *
[EMAIL PROTECTED]
*Sent:* Friday, April 27, 2007 9:04 AM
*To:* [EMAIL PROTECTED]
*Cc:* [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
*Subject:* Re: [WiX-users] Logging in a custom action
I found a co-worker lucky enough to have 05 insta
CTED] [mailto:[EMAIL PROTECTED] On Behalf Of LEMIRE, JOHN
Sent: Friday, April 27, 2007 9:44 AM
To: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
I've lost track of what your CA actually does (if it was ever mentioned) but
have you tried using a dummy exe shell an
D]; [EMAIL PROTECTED];
WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
You may have other problems (like dependencies that aren't being met
thus your code is immediately failing) but assuming that your code is
running correctly, you're not going to see any m
191EE&displaylang=en
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 9:04 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Log
"DoAction". Windows Installer
restriction.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 6:52 AM
To: Rob Mensching; [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
I'll try to answer your questi
[EMAIL PROTECTED] wrote:
Is there any way to determine from the log why a CA is failing to
execute, if it appears that its never even getting into the CA in the
first place?
That almost always means that the DLL has a dependency not being met,
which almost always means you're linking with
[EMAIL PROTECTED] wrote:
No, I haven't tried that. The WiX chm explicitly says you need VS
2005 to build.
I guess I could try it with 03 anyways.
That's why I'm not sure you can use wcautil.lib from VS 7.1.
--
sig://boB
http://bobs.org
---
in the
first place?
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 2:18 AM
To: Rowland, Chris
Cc: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
[EMAIL PROTECTED] wrote:
I
='Microsoft.VC80.CRT'
version='8.0.50608.0' ... encountered; ignored
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 12:29 AM
To: Rowland, Chris; [EMAIL PROTECTED];
WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users
users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
[EMAIL PROTECTED] wrote:
I was able to resolve my build errors by "defining" everything missing
myself (to /**/ ).
I read that they might be defined by default in VS05, but not in VS03
(what I'm using
en the user clicks the next button in a custom dialog.
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 12:29 AM
To: Rowland, Chris; [EMAIL PROTECTED];
WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
Are you dynamically
[EMAIL PROTECTED] wrote:
I was able to resolve my build errors by "defining" everything missing
myself (to /**/ ).
I read that they might be defined by default in VS05, but not in VS03
(what I'm using.)
Did you rebuild wcautil.lib? I'm not sure whether you're going to run
into problems
CustomAction. When is
it being scheduled?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 2:20 PM
To: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
Yeah, the error was in the custom
ECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
_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.
-
; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
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] [m
d to use the mangled name...
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 2:20 PM
To: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
Ye
Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 5:20 PM
To: Brian Simoneau; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
Yeah, the error was in th
debug :-)
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 4:57 PM
To: Rowland, Chris; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
Was the error in the custom action itself? If so, then yo
: RE: [WiX-users] Logging in a custom action
After an obscene amount of headbanging, I finally managed to get
it to build (with warnings) with the almighty T() call.
Unfortunately that resulted in a CA that caused the installer to
quit due to an error. If
-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
_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 Si
:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 3:05 PM
To: Brian Simoneau; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
It's an immediate CA. I tried wrapping my strings with _T() but
_T is not de
efine __inout /* ? */
#define __in_bcount(THING) /* ? */
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 2:59 PM
To: Rowland, Chris; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
That code look
2:31 PM
To: Brian Simoneau; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
Thanks for the continuing advice. I'm still not seeing any log
out put though. I've commented out the guts of my CA, so now I
e in some way as
well?
Thanks again for your help. Google doesn't reveal much on this subject
:-(
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 1:58 PM
To: Rowland, Chris; WiX-users@lists.sourceforge.net
Subject: RE: [
PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 1:41 PM
To: Brian Simoneau; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
I was able to resolve my build errors by "defining" everythi
ECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 12:42 PM
To: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
Thanks, that looks like what I wanted.
I'm having trouble linking everyth
__
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 25, 2007 4:20 PM
To: Rowland, Chris; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Logging in a custom action
If you are writing a C++ custom action, then the WcaLog function in
wcautil will write to t
is used by the
ExitOnXxx macros in WiX CusotmActions.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LEMIRE, JOHN
Sent: Wednesday, April 25, 2007 2:15 PM
To: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Logging in a custom action
Note huge caveat that ::MsiProc
I can't say if it overcomes this
shortcoming...
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Wednesday, April 25, 2007 1:48 PM
To: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Loggin
::MsiProcessMessage() or WcaProcessMessage() if you're using wcautil.lib to
hide some of the trickier parts of the MSI API for CustomActions.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, April 25, 2007 1:08 PM
To: WiX-users@lists.sourceforge.ne
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: W
Dana Gutride wrote:
> When the already installed version was created, were those
> uninstall custom actions included in it? The installed MSI
> is called to handle the uninstall sequence, any changes you
> make to your uninstall sequence will only affect the new
> installers you create.
>
>
Are you sure you're looking at the right property? I mean,
NEWERVERSIONDETECTED is a strange property name for the detection of an
*older* version.
That said, the uninstall of the old version should be in the log, masrked
with (N) for nested as opposed to (c) for client side and (s) for server
Andre:
When the already installed version was created, were those uninstall custom
actions included in it? The installed MSI is called to handle the uninstall
sequence, any changes you make to your uninstall sequence will only affect
the new installers you create.
As far as your logging questio
83 matches
Mail list logo
