Re: [WiX-users] logging
Hello Martin, Thank you for your assistance, unfortunately this is still not working. If anyone has any solution to this problem, then I would love to hear it!! Thanks again, Dave 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: 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 redirection in DOS should happen at the end of the line: RunWait($WIX_FOLDER '\candle.exe -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs myfile.txt ',$BUILD_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 trying to implement it into my calls, but sadly it does not seem to work. I have tried the redirecting with a simple cmd call and it works fine. However I am creating an automation process using autoit, and im not sure if I would be using the redirection correctly. Autoit script: RunWait($WIX_FOLDER '\candle.exe myfile.txt -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE) If anyone could point me in the right direction I would be incredibly 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 Subject: Re: [WiX-users] logging Something like this may help: http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scri pts/ 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 the calls, which causes the command prompt to close very quickly after the code has been run. Thanks in advance. PS thank you Tonny Erjomin for the help on language support David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474 846p6475377.html Sent from the wix-users mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's
Re: [WiX-users] logging
Ive not used AutoIt but a quick look suggests it's using createprocess. To
get output redirection on a command line you need to be in a DOS box.
Try ('cmd \c ' $WIX_FOLDER '\candle.exe..
You might have to fiddle with quote marks if there are spaces in your path.
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
Hello Martin,
Thank you for your assistance, unfortunately this is still not working.
If anyone has any solution to this problem, then I would love to hear it!!
Thanks again,
Dave
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: 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 redirection in DOS
should happen at the end of the line:
RunWait($WIX_FOLDER '\candle.exe -dmanufacturer='$MANUFACTURER_NAME'
-dproductName='$productName' -dcabName='$CABINET_NAME'.cab
-dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out
'$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs myfile.txt
',$BUILD_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 trying to implement it into my calls, but sadly it does not seem
to work.
I have tried the redirecting with a simple cmd call and it works fine.
However I am creating an automation process using autoit, and im not sure if
I would be using the redirection correctly.
Autoit script:
RunWait($WIX_FOLDER '\candle.exe myfile.txt
-dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName'
-dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode'
-dproductGUID='$productCode' -out '$BUILD_FOLDER'\
'$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE)
If anyone could point me in the right direction I would be incredibly
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
Subject: Re: [WiX-users] logging
Something like this may help:
http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scri
pts/
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 the calls, which causes the command prompt to close
very quickly after the code has been run.
Thanks in advance.
PS thank you Tonny Erjomin for the help on language support David Amey
The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24
9DR
T: +44 (0)1483 799200 F: +44 (0)1483 799111
--
EditLive Enterprise is the world's most technically advanced
content authoring tool. Experience the power of Track Changes, Inline
Image Editing and ensure content is compliant with Accessibility
Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474
846p6475377.html
Sent from the wix-users mailing list archive at Nabble.com.
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image Editing
and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image Editing
and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] logging
Hi Dave, Thank you for this link. I have been trying to implement it into my calls, but sadly it does not seem to work. I have tried the redirecting with a simple cmd call and it works fine. However I am creating an automation process using autoit, and im not sure if I would be using the redirection correctly. Autoit script: RunWait($WIX_FOLDER '\candle.exe myfile.txt -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE) If anyone could point me in the right direction I would be incredibly 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 Subject: Re: [WiX-users] logging 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 the calls, which causes the command prompt to close very quickly after the code has been run. Thanks in advance. PS thank you Tonny Erjomin for the help on language support David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474846p6475377.html Sent from the wix-users mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] logging
Hi David, I am not expert in candle and light but I believe that redirection in DOS should happen at the end of the line: RunWait($WIX_FOLDER '\candle.exe -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs myfile.txt ',$BUILD_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 trying to implement it into my calls, but sadly it does not seem to work. I have tried the redirecting with a simple cmd call and it works fine. However I am creating an automation process using autoit, and im not sure if I would be using the redirection correctly. Autoit script: RunWait($WIX_FOLDER '\candle.exe myfile.txt -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE) If anyone could point me in the right direction I would be incredibly 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 Subject: Re: [WiX-users] logging Something like this may help: http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scri pts/ 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 the calls, which causes the command prompt to close very quickly after the code has been run. Thanks in advance. PS thank you Tonny Erjomin for the help on language support David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474 846p6475377.html Sent from the wix-users mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] logging
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 the calls, which causes the command prompt to close very quickly after the code has been run. Thanks in advance. PS thank you Tonny Erjomin for the help on language support David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474846p6475377.html Sent from the wix-users mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging while uninstalling from Control Panel
Thanks guys. So looks like the only option is to enable logging in registry
manually that will create log files for any program when uninstalled from
Control Panel. I guess I have to live with it.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Saturday, August 07, 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 UninstallString to
MsiExec.exe /x {blah} /l*v C:\q.txt.
No, ARP ignores that string.
--
sig://boB
http://joyofsetup.com/
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
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 UninstallString to MsiExec.exe /x
{blah} /l*v C:\q.txt.
No, ARP ignores that string.
--
sig://boB
http://joyofsetup.com/
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
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: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: saikodi [mailto:saik...@hotmail.com] Sent: 06 August 2010 07:51 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging while uninstalling from Control Panel Hello All, If the user uninstalls an application from Control Panel, is it possible to provide an uninstallation log file somehow for the uninstallation process? If so, how would I provide that log file name and location? Please advise. Thanks, Sai Kodi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Logging-wh ile-uninstalling-from-Control-Panel-tp5379515p5379515.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 know how that works. I want to be able to create a log file during uninstallation only at a custom location with a custom file name. I don't want to enable logging for all the installers. I just want to log the uninstallation of my application. Using msiexec, I can do that using: Msiexec.exe /x [productcode] /l*v uninstall.log How can I achieve a similar behavior while uninstalling from Control Panel? Thanks, Sai Kodi -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.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: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: saikodi [mailto:saik...@hotmail.com] Sent: 06 August 2010 07:51 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging while uninstalling from Control Panel Hello All, If the user uninstalls an application from Control Panel, is it possible to provide an uninstallation log file somehow for the uninstallation process? If so, how would I provide that log file name and location? Please advise. Thanks, Sai Kodi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Logging-wh ile-uninstalling-from-Control-Panel-tp5379515p5379515.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging while uninstalling from Control Panel
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 from Control Panel Hi Pally, That's not what I am looking for. I have already done that search and I know how that works. I want to be able to create a log file during uninstallation only at a custom location with a custom file name. I don't want to enable logging for all the installers. I just want to log the uninstallation of my application. Using msiexec, I can do that using: Msiexec.exe /x [productcode] /l*v uninstall.log How can I achieve a similar behavior while uninstalling from Control Panel? Thanks, Sai Kodi -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.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: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: saikodi [mailto:saik...@hotmail.com] Sent: 06 August 2010 07:51 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging while uninstalling from Control Panel Hello All, If the user uninstalls an application from Control Panel, is it possible to provide an uninstallation log file somehow for the uninstallation process? If so, how would I provide that log file name and location? Please advise. Thanks, Sai Kodi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Logging-wh ile-uninstalling-from-Control-Panel-tp5379515p5379515.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging while uninstalling from Control Panel
I don't think it's possible to enable logging at uninstall time from the control panel to a custom location for a very specific package. _As I understand it_ the control panel simply does the equivalent of Msiexec.exe /x [productcode] That's it. Your only option is to enable logging for all installers *OR* uninstall from the command line. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please 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] Logging while uninstalling from Control Panel Hi Pally, That's not what I am looking for. I have already done that search and I know how that works. I want to be able to create a log file during uninstallation only at a custom location with a custom file name. I don't want to enable logging for all the installers. I just want to log the uninstallation of my application. Using msiexec, I can do that using: Msiexec.exe /x [productcode] /l*v uninstall.log How can I achieve a similar behavior while uninstalling from Control Panel? Thanks, Sai Kodi -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.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: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: saikodi [mailto:saik...@hotmail.com] Sent: 06 August 2010 07:51 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging while uninstalling from Control Panel Hello All, If the user uninstalls an application from Control Panel, is it possible to provide an uninstallation log file somehow for the uninstallation process? If so, how would I provide that log file name and location? Please advise. Thanks, Sai Kodi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Logging-wh ile-uninstalling-from-Control-Panel-tp5379515p5379515.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in deferred CA
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! I was wondering, how can i log stuff within a deferred custom action, since i can't use session.Log? Regards, Stelios -- Stelios Kyprou Systems Engineer Formicary - delivering quality financial technology solutions(TM) www.formicary.net This message is confidential and may be privileged. It is intended solely for the named addressee. If you are not the intended recipient, please inform us. Any unauthorised dissemination, distribution or copying hereof is prohibited. Formicary Limited registered office in England and Wales, address 1 Taillar Road, Hedon, East Yorkshire HU12 8GU, registration number 3894343, VAT number 747644304, does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging Error
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 C:/Documents and Settings/name/My Documents/tfuInstaller.txt I get an error message that states: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer Package. If I go to the directory and run the .msi from there, the installer runs. Am I doing something wrong? -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging Error
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 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 C:/Documents and Settings/name/My Documents/tfuInstaller.txt I get an error message that states: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer Package. If I go to the directory and run the .msi from there, the installer runs. Am I doing something wrong? -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Note: The information contained in this message may be privileged and confidential and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging information
Unfortunately, *I* personally don't know how to do dcomcnfg. The ComPlus Extension, http://wix.sourceforge.net/manual-wix3/complus_xsd_index.htm, might be appropriate here but I don't know the details of its usage. Perhaps somebody more knowledgeable can provide some guidance. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.com] Sent: 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 and interface ids but still it is not registering. We want to see our COM exes into dcomcnfg. Our COM exes only showing in dcomcinfg after using RegServer command. So can you please suggest me what I have to do to show my COM exes into dcomcnfg (or register similar to RegServer using WIX) Thanks, Rahul From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Fri 7/9/2010 3:55 PM To: General 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 things for you: 1.) Hide the command prompt window that shows up for console applications. 2.) Capture your console application's output and include it in the MSI log file. See the WiX documentation to read up on CAQuietExec. Of course, I would *highly* discourage you from using the custom action to register your application as support for repair, uninstall, and all the different types of rollback are more difficult to handle (you're allowing a blackbox to execute that _could_ do anything). That said, if you still want to register your application using the custom action, then consider scheduling it between InstallInitialize and InstallFinalize and make the custom action deferred. Obviously you'll want to schedule it at least after InstallFiles. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com ??Please consider the environment before printing this e-mail -Original Message- From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.com] Sent: Friday, July 09, 2010 1:53 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging information Hi, I am running following custom action which runs /RegServer command. File Id='distributeserver' Name=DISTRIBUTESERVERFILE src=f:\Program Files\Ambit ALM 6\ALMEngine\distributionserver.exe / CustomAction Id='DISTRIBUTESERVERCUSTOMACTION' FileKey='distributeserver' ExeCommand=' /RegServer' Execute ='immediate' Return='ignore'/ InstallExecuteSequence Custom Action='DISTRIBUTESERVERCUSTOMACTION' After='InstallFinalize' / /InstallExecuteSequence I am ruunig msi using command line msiexec.exe /i installer.msi file:///\\pc307\path\alm_installer.msi file://pc307/path/alm_installer.msi/L*v c: install.txt However I am not seeing what exactly command executed by my custom action. Can anyone know how to log customaction in log file ( means what is exact command fired by custom action). Thanks, Rahul Ekbote Senior Software Engineer * SunGard * ALM * Bancware * SunGard Technology Services (India), Meridian Plaza, S B Road, Shivajinagar, Pune 411016. Direct Tel +91-20-25606237 * Main Tel +91-20-30238000 * Fax +91-20-25606222 * rahul.ekb...@sungard.com mailto:rahul.ekb...@sos.sungard.com * www.sungard.com http://www.sungard.com/bancware /bancware P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you receive this e-mail in error, please notify the sender and delete this e-mail from your system. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging information
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 console application's output and include it in the MSI log file. See the WiX documentation to read up on CAQuietExec. Of course, I would *highly* discourage you from using the custom action to register your application as support for repair, uninstall, and all the different types of rollback are more difficult to handle (you're allowing a blackbox to execute that _could_ do anything). That said, if you still want to register your application using the custom action, then consider scheduling it between InstallInitialize and InstallFinalize and make the custom action deferred. Obviously you'll want to schedule it at least after InstallFiles. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.com] Sent: Friday, July 09, 2010 1:53 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging information Hi, I am running following custom action which runs /RegServer command. File Id='distributeserver' Name=DISTRIBUTESERVERFILE src=f:\Program Files\Ambit ALM 6\ALMEngine\distributionserver.exe / CustomAction Id='DISTRIBUTESERVERCUSTOMACTION' FileKey='distributeserver' ExeCommand=' /RegServer' Execute ='immediate' Return='ignore'/ InstallExecuteSequence Custom Action='DISTRIBUTESERVERCUSTOMACTION' After='InstallFinalize' / /InstallExecuteSequence I am ruunig msi using command line msiexec.exe /i installer.msi file:///\\pc307\path\alm_installer.msi /L*v c: install.txt However I am not seeing what exactly command executed by my custom action. Can anyone know how to log customaction in log file ( means what is exact command fired by custom action). Thanks, Rahul Ekbote Senior Software Engineer * SunGard * ALM * Bancware * SunGard Technology Services (India), Meridian Plaza, S B Road, Shivajinagar, Pune 411016. Direct Tel +91-20-25606237 * Main Tel +91-20-30238000 * Fax +91-20-25606222 * rahul.ekb...@sungard.com mailto:rahul.ekb...@sos.sungard.com * www.sungard.com http://www.sungard.com/bancware /bancware P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you receive this e-mail in error, please notify the sender and delete this e-mail from your system. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 and interface ids but still it is not registering. We want to see our COM exes into dcomcnfg. Our COM exes only showing in dcomcinfg after using RegServer command. So can you please suggest me what I have to do to show my COM exes into dcomcnfg (or register similar to RegServer using WIX) Thanks, Rahul From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Fri 7/9/2010 3:55 PM To: General 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 things for you: 1.) Hide the command prompt window that shows up for console applications. 2.) Capture your console application's output and include it in the MSI log file. See the WiX documentation to read up on CAQuietExec. Of course, I would *highly* discourage you from using the custom action to register your application as support for repair, uninstall, and all the different types of rollback are more difficult to handle (you're allowing a blackbox to execute that _could_ do anything). That said, if you still want to register your application using the custom action, then consider scheduling it between InstallInitialize and InstallFinalize and make the custom action deferred. Obviously you'll want to schedule it at least after InstallFiles. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com ??Please consider the environment before printing this e-mail -Original Message- From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.com] Sent: Friday, July 09, 2010 1:53 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging information Hi, I am running following custom action which runs /RegServer command. File Id='distributeserver' Name=DISTRIBUTESERVERFILE src=f:\Program Files\Ambit ALM 6\ALMEngine\distributionserver.exe / CustomAction Id='DISTRIBUTESERVERCUSTOMACTION' FileKey='distributeserver' ExeCommand=' /RegServer' Execute ='immediate' Return='ignore'/ InstallExecuteSequence Custom Action='DISTRIBUTESERVERCUSTOMACTION' After='InstallFinalize' / /InstallExecuteSequence I am ruunig msi using command line msiexec.exe /i installer.msi file:///\\pc307\path\alm_installer.msi file://pc307/path/alm_installer.msi /L*v c: install.txt However I am not seeing what exactly command executed by my custom action. Can anyone know how to log customaction in log file ( means what is exact command fired by custom action). Thanks, Rahul Ekbote Senior Software Engineer * SunGard * ALM * Bancware * SunGard Technology Services (India), Meridian Plaza, S B Road, Shivajinagar, Pune 411016. Direct Tel +91-20-25606237 * Main Tel +91-20-30238000 * Fax +91-20-25606222 * rahul.ekb...@sungard.com mailto:rahul.ekb...@sos.sungard.com * www.sungard.com http://www.sungard.com/bancware /bancware P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you receive this e-mail in error, please notify the sender and delete this e-mail from your system. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from XML file?
When (where) do you want the log message to appear in the log file? dB. @ dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: Slide [mailto:slide.o@gmail.com] Sent: Wednesday, December 02, 2009 9: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 log if I did: msiexec /i myinstaller.msi /l* install.log I would like to do something like this: Component Guid=SOME-GUID-HERE Log Level=Info Message=Installing some component...MYPROPERTY=[MYPROPERTY]/ /Component Thanks, slide On Wed, Dec 2, 2009 at 6:44 PM, Blair os...@live.com wrote: 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.com] Sent: Wednesday, December 02, 2009 11:15 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging from XML file? Is it possible to log something to the installer log file from the XML definition? Thanks, slide -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- slide-o-blog http://slide-o-blog.blogspot.com/ -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from XML file?
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.com] Sent: Wednesday, December 02, 2009 11:15 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging from XML file? Is it possible to log something to the installer log file from the XML definition? Thanks, slide -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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: Component Guid=SOME-GUID-HERE Log Level=Info Message=Installing some component...MYPROPERTY=[MYPROPERTY]/ /Component Thanks, slide On Wed, Dec 2, 2009 at 6:44 PM, Blair os...@live.com wrote: 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.com] Sent: Wednesday, December 02, 2009 11:15 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging from XML file? Is it possible to log something to the installer log file from the XML definition? Thanks, slide -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- slide-o-blog http://slide-o-blog.blogspot.com/ -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from XML file?
Check out the MsiLogging property in the MSI SDK. On Wed, Dec 2, 2009 at 6:09 PM, Slide slide.o@gmail.com 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 like to do something like this: Component Guid=SOME-GUID-HERE Log Level=Info Message=Installing some component...MYPROPERTY=[MYPROPERTY]/ /Component Thanks, slide On Wed, Dec 2, 2009 at 6:44 PM, Blair os...@live.com wrote: 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.com] Sent: Wednesday, December 02, 2009 11:15 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging from XML file? Is it possible to log something to the installer log file from the XML definition? Thanks, slide -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- slide-o-blog http://slide-o-blog.blogspot.com/ -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from XML file?
You present a database of how you wish the world to be configured for your installation. Windows Installer takes that database and creates a script from it. That script first analyzes which components need what (to be installed, upgraded, repaired, removed) and then a script is written by checking the impact of each of the component's resources, then the script is run (in resource-order, not component-order). Let me illustrate with a simple-yet-contrived simplistic example: MSI File: Component A File A1 Registry R1 Component B Registry R2 Registry R3 Component C File C1 File C2 Registry R4 Imagine that in this example Component B was already installed from another product, and Component C is upgrading from a previous product installation (Component A is new). Windows Installer first determines that Component A and C will be installed, and B will be left alone. Then it will look to see if any registry entries need to be removed due to components that are being either installed or removed, and those get written into the script (none in our example). Then any files that need to be removed for similar reasons (none in our example). Then any files that need to be written from components being installed (A1, C1, C2), then any registry entries (R4). That is what all of the actions sequenced between InstallInitialize and InstallFinalize do. So, the built script for our example will have 4 entries in this order: Write File A1 Write File C1 - overwriting whatever may have already been there Write File C2 - overwriting whatever may have already been there Write Registry R1 Write Registry R4 - overwriting whatever may have already been there So, there is no moment of installing Component A (with everything in it) vs. a different moment of installing Component C (with everything in that), for instance. The conversion from described state to actual state is caused by this analysis of components (the atomic units of installation) and the resources connected to those components and is the heart of Windows Installer's state engine. It is possible to send messages to the UI and/or to the log to show state (that is how you can get Installing Files.. or even Installing path-of-file messages. In fact, the UI and the logging share the same code inside the Installer engine, so anything that can be sent to the one can be sent in a similar way to the other (for the most part). The question becomes one of when in the script you want it sent. -Original Message- From: Slide [mailto:slide.o@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 log if I did: msiexec /i myinstaller.msi /l* install.log I would like to do something like this: Component Guid=SOME-GUID-HERE Log Level=Info Message=Installing some component...MYPROPERTY=[MYPROPERTY]/ /Component Thanks, slide On Wed, Dec 2, 2009 at 6:44 PM, Blair os...@live.com wrote: 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.com] Sent: Wednesday, December 02, 2009 11:15 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Logging from XML file? Is it possible to log something to the installer log file from the XML definition? Thanks, slide -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- slide-o-blog http://slide-o-blog.blogspot.com/ -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend
Re: [WiX-users] Logging
Sorry I wasn't being clear.. I am using light in a c# app. And this is what
is happening:
Process light = new Process();
light.StartInfo.FileName = WiX toolset\light.exe;
light.StartInfo.Arguments = \ + OutputFolder +.+ \WiXOutput.wixobj +
\ + -out + \ + OutputFolder + . + projectName + .msi + \
+ build2.log + -ext WixUIExtension -loc + \ + OutputFolder + @\
+ ...\Language.xml + \;
light.Start();
while (!light.HasExited)
{
Application.DoEvents();
Thread.Sleep(20);
}
When I debug and copy the light.StartInfo.Arguments string and paste it in
the console, it works great. But not when I run my app. like I usually 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
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: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging
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
/Simon
On Mon, Oct 6, 2008 at 1:15 PM, Peter Vestergaard [EMAIL PROTECTED]
wrote:
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 args 1stdout.txt 2stderr.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
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in
the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org
Re: [WiX-users] Logging
yes, shell redirection does not work in this case.
In that case you should use
ProcessStartInfo.RedirectStandardOutput / .RedirectStandardError
and then you can read the output from
light.StandardOutput and light.StandardError
/Simon
On Tue, Oct 7, 2008 at 11:22 AM, Peter Vestergaard [EMAIL PROTECTED]wrote:
Sorry I wasn't being clear.. I am using light in a c# app. And this is what
is happening:
Process light = new Process();
light.StartInfo.FileName = WiX toolset\light.exe;
light.StartInfo.Arguments = \ + OutputFolder +.+ \WiXOutput.wixobj
+
\ + -out + \ + OutputFolder + . + projectName + .msi + \
+ build2.log + -ext WixUIExtension -loc + \ + OutputFolder + @\
+ ...\Language.xml + \;
light.Start();
while (!light.HasExited)
{
Application.DoEvents();
Thread.Sleep(20);
}
When I debug and copy the light.StartInfo.Arguments string and paste it in
the console, it works great. But not when I run my app. like I usually 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
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: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging
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).aspxhttp://msdn.microsoft.com/en-us/library/ms171470%28VS.80%29.aspx
/Simon
On Mon, Oct 6, 2008 at 1:15 PM, Peter Vestergaard
[EMAIL PROTECTED]
wrote:
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 args 1stdout.txt 2stderr.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
-
This SF.Net email is sponsored by the Moblin Your Move
Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in
the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in
the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org
Re: [WiX-users] Logging
Thank you all! Great help!
2008/10/7 Simon Dahlbacka [EMAIL PROTECTED]
yes, shell redirection does not work in this case.
In that case you should use
ProcessStartInfo.RedirectStandardOutput / .RedirectStandardError
and then you can read the output from
light.StandardOutput and light.StandardError
/Simon
On Tue, Oct 7, 2008 at 11:22 AM, Peter Vestergaard [EMAIL PROTECTED]
wrote:
Sorry I wasn't being clear.. I am using light in a c# app. And this is
what
is happening:
Process light = new Process();
light.StartInfo.FileName = WiX toolset\light.exe;
light.StartInfo.Arguments = \ + OutputFolder +.+
\WiXOutput.wixobj
+
\ + -out + \ + OutputFolder + . + projectName + .msi +
\
+ build2.log + -ext WixUIExtension -loc + \ + OutputFolder +
@\
+ ...\Language.xml + \;
light.Start();
while (!light.HasExited)
{
Application.DoEvents();
Thread.Sleep(20);
}
When I debug and copy the light.StartInfo.Arguments string and paste it
in
the console, it works great. But not when I run my app. like I usually 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
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: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Logging
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
http://msdn.microsoft.com/en-us/library/ms171470%28VS.80%29.aspx
/Simon
On Mon, Oct 6, 2008 at 1:15 PM, Peter Vestergaard
[EMAIL PROTECTED]
wrote:
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 args 1stdout.txt 2stderr.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
-
This SF.Net email is sponsored by the Moblin Your Move
Developer's
challenge
Build the coolest Linux based applications with Moblin SDK
win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere
in
the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
-
This SF.Net email is sponsored by the Moblin Your Move
Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in
the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in
the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored
Re: [WiX-users] Logging
There's the traditional method of redirecting the output: candle args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from a Custom Action during the UI phase
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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging
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 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 args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging
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 /Simon On Mon, Oct 6, 2008 at 1:15 PM, Peter Vestergaard [EMAIL PROTECTED] wrote: 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 args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging
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 args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging
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_COMMON_PATH.wixobj Add_Common_Bin_To_Path.wixobj -loc Common\CommonSettings\Common-E.wxl -loc English.wxl -out DBS.msi 1out.txt 2err.txt Currently there's no outout so both files are empty, but if I remove the -nologo flag then out.txt contains: Microsoft (R) Windows Installer Xml Linker version 2.0.4415.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. Hope that helps, Rob Peter Vestergaard wrote: 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 args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging
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 1out.txt 2err.txt 2008/10/6 Rob Hamflett [EMAIL PROTECTED] 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_COMMON_PATH.wixobj Add_Common_Bin_To_Path.wixobj -loc Common\CommonSettings\Common-E.wxl -loc English.wxl -out DBS.msi 1out.txt 2err.txt Currently there's no outout so both files are empty, but if I remove the -nologo flag then out.txt contains: Microsoft (R) Windows Installer Xml Linker version 2.0.4415.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. Hope that helps, Rob Peter Vestergaard wrote: 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 args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging
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\...\Installer.msi -ext WixUIExtension -loc C:\Projects\...\Language.xml 1out.txt 2err.txt 2008/10/6 Rob Hamflett [EMAIL PROTECTED] 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_COMMON_PATH.wixobj Add_Common_Bin_To_Path.wixobj -loc Common\CommonSettings\Common-E.wxl -loc English.wxl -out DBS.msi 1out.txt 2err.txt Currently there's no outout so both files are empty, but if I remove the -nologo flag then out.txt contains: Microsoft (R) Windows Installer Xml Linker version 2.0.4415.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. Hope that helps, Rob Peter Vestergaard wrote: 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 args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging
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 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 /Simon On Mon, Oct 6, 2008 at 1:15 PM, Peter Vestergaard [EMAIL PROTECTED] wrote: 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 args 1stdout.txt 2stderr.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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from a Custom Action during the UI phase
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. smile/ Of course not. I had half guessed it was something like this anyway. I guess it's a matter of inserting a MessageBox call at the top of my CA and attaching a debugger then. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from a Custom Action during the UI phase
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 processing issue inside them. I think this is documented in some small print somewhere. PS: Please don't shoot the messenger. smile/ Of course not. I had half guessed it was something like this anyway. I guess it's a matter of inserting a MessageBox call at the top of my CA and attaching a debugger then. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Teleoperate a roving mobile robot from the web: http://www.swampgas.com/robotics/rover.html - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from a Custom Action during the UI phase
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. smile/ Of course not. I had half guessed it was something like this anyway. I guess it's a matter of inserting a MessageBox call at the top of my CA and attaching a debugger then. 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 Urman - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from a Custom Action during the UI phase
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 OutputDebugString with the information you want to log and then run something like DebugView to see the debug output stream. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging from a Custom Action during the UI phase
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. smile/ -Original Message- From: John Hall [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 01, 2008 02:05 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Logging from a Custom Action during the UI phase In my installer I have some C++ custom actions that log to the main MSI log file using MsiProcessMessage. I'm now writing a CA that is executed on a button press in the UI as the user leaves the feature selection dialog. However, none of my debug output is appearing in the log. Is there a reason why this doesn't work? Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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.) Did you rebuild wcautil.lib? I'm not sure whether you're going to run into problems mixing an '05 static lib with '03. -- sig://boB http://bobs.org - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
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] 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 the DLL version of the runtime library and it's not present on the target. Set the compiler options to link with the static CRT and your life will be much simpler (at least as far as CA DLLs go). -- sig://boB http://bobs.org - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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're right, it's for the RTM. The embedded versions are still at 8.0.50727.42, sigh. Phil Wilson From: Simon Dahlbacka [mailto:[EMAIL PROTECTED] Sent: 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 your custom action (writtten in VS 2005, yes?) works. That'll isolate it to a C++ dependency on the 8.0 CRT etc http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4 C13-9C99-220B62A191EEdisplaylang=en Unfortunately this is the pre-SP1 version of the runtime, and there doesn't seem to exist a link to the post-SP1 version... 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] Logging in a custom action I found a co-worker lucky enough to have 05 installed and built my dll there (easy as pie) but the CA still bails, apparently before it has a chance to log anything. 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? 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 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 mixing an '05 static lib with '03. -- sig://boB http://bobs.org - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
Ah, ok, the one in [ProgramFilesFolder]Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\vcredist_x86 is up to date with SP1. While I'm on this subject, I've noticed that Orca will unconditionally change modify dates on merge modules. You don't need to alter them in any way, just open and close. The result is that they look like data files that have been modified, and in this particular case it means that VS 2005 SP1 will not update you with new versions of the merge modules because of the MSI update rules. Phil Wilson From: [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're right, it's for the RTM. The embedded versions are still at 8.0.50727.42, sigh. Phil Wilson From: Simon Dahlbacka [mailto:[EMAIL PROTECTED] Sent: 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 your custom action (writtten in VS 2005, yes?) works. That'll isolate it to a C++ dependency on the 8.0 CRT etc http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4 C13-9C99-220B62A191EEdisplaylang=en Unfortunately this is the pre-SP1 version of the runtime, and there doesn't seem to exist a link to the post-SP1 version... 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] Logging in a custom action I found a co-worker lucky enough to have 05 installed and built my dll there (easy as pie) but the CA still bails, apparently before it has a chance to log anything. 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? 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 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 mixing an '05 static lib with '03. -- sig://boB http://bobs.org - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
Dependency Walker (depends.exe) is part of the Platform SDK, ships with Visual Studio (in Common7\Tools\Bin) and is downloadable from http://www.dependencywalker.com/. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: 27 April 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 figure out how heavy a piece of code is. Fewer dependencies the better. From: [EMAIL PROTECTED] [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 and having it do a load lib / getprocaddress on your CA? This may be a way to find a dependency problem on that box. I once ran into one trying to use a winsock api on a W2K box. WS2_32.dll was there but the older version didn't support the method I was using.. (::GetAddrInfo I think) _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, April 27, 2007 9:18 AM To: [EMAIL PROTECTED]; [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 messages. Why? Your answer to my last question. ::MsiProcessMessage() will not work from a UI 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 questions, but this is my first experience doing any sort of work in Visual Studio, so I'm largely unfamiliar. I'm also using 2003, which seems that is partially contributing to my problems. Basically the installer seemed to be working, except on one particular vista 64 machine where it looks like it is failing in a particular CA. At that point I decided I needed to find out how to do some logging from within the Custom Action so I could diagnose the problem beyond 'returned status 3.' That leads me to believe that any dependency that might not be met was introduced when I included wcautil.lib and dutil.lib. In order to get this to compile, I also had to build without /clr. Not something I'm familiar with, but I'm aware of the managed code is bad in CAs mantra, so that sounded reasonable. Are you dynamically linking against MSVCRT? I'm not sure. how might I find out? It is possible your CustomAction has some dependency and failing to load right off the bat. Would it be that the DLL itself has a dependency ( as opposed to the CA) because that could be the case. From trying to isolate the problem, the CA itself currently has nothing but return ERROR_SUCCES and it still dies. Also, can you share the .wxs authoring for the CustomAction Is this what you mean? CustomAction Id='VerifyLicenseDir' BinaryKey='LicenseFileUtils' DllEntry='VerifyLicenseDir' / When is it being scheduled? It is run when 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 linking against MSVCRT? More specifically, what are the dependencies your CustomAction has on the OS and are they all met? It is possible your CustomAction has some dependency and failing to load right off the bat. Also, can you share the .wxs authoring for the 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 action. (It returned the value 3) I had tried to attach to msiexec.exe before to debug, but didn't make any progress with that. Can you show me how you fired off the MessageBox from within your CA? This is a lot of debugging just so I can 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 you
Re: [WiX-users] Logging in a custom action
I was able to build with a colleague's VC2005 install with no issues (build wise) but in trying to move my project into VC++ 2005 Express on my own system, I get linkage errors. 1wcautil.lib(wcalog.obj) : error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function int __stdcall IsVerboseLogging(void) (?IsVerboseLogging@@YGHXZ) In my project settings I have 2 additional Include directories, and 2 additonal library directories each, corresponding to the wix2 sdk and win2k3 platform sdk include lib directories. Is this evidence of 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 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 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
After installing Visual Studio 2005 SP1, the WinSxS Merge Modules will be available in [ProgramFilesFolder]Common Files\Merge Modules. But beware of the Orca behavior. Any one of the RTM versions that you looked at with Orca won't be updated by installing SP1 because Orca unconditionally changes the modify date. That makes it different from the creation date, therefore SP1 won't replace it. I'm not talking about changing the merge module - just simply opening it with Orca will effectively disable the SP1 update of that merge module. 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 will be available in [ProgramFilesFolder]Common Files\Merge Modules. Unless you had a pre-release version of Visual Studio 2005 installed on your system. There's a bug where only the 64-bit Merge Modules would be updated by Visual Studio 2005 SP1, because pre-release Visual Studio 2005 did not uninstall the 32-bit Merge Modules. Visual Studio 2005 SP1 then doesn't install them. So grab them from another system and overwrite the pre-release versions. They're absolute terrible at verification, however, throwing up every warning imaginable in InstallShield 12 (I know, I know...). Joel Peterson Quality Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Dahlbacka Sent: Friday, April 27, 2007 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 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 with SP1), FWIW, I still find it suboptimal that Microsoft distributes an old version on the web... - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
Thanks, that looks like what I wanted. I'm having trouble linking everything correctly though, and I get a ton of errors in wcautil.h, like E:\Program Files\WiX\sdk\inc\wcautil.h(48): error C2065: '__in' : undeclared identifier And E:\Program Files\WiX\sdk\inc\wcautil.h(48): error C2182: 'WcaGlobalInitialize' : illegal use of type 'void' I've tried to include dutil.lib and wcautil.lib. Is there something else that needs to be configured to use wcautil.lib (specifically WcaLog)? 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 the install log or show you how to do it yourself. -Brian Simoneau - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
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.)
However, I rebuilt my installer with the new DLL and ran it with *cv
logging, and I still don't see anything.
The CA call seems to execute properly in all other regards.
I put a WcaLog statement as the first line in my method.
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
Here's the section of log where I expected to see some output.
MSI (c) (4C:98) [13:21:11:484]: Doing action: VerifyLicenseDir
MSI (c) (4C:98) [13:21:11:484]: Note: 1: 2205 2: 3: ActionText
Action 13:21:11: VerifyLicenseDir.
Action start 13:21:11: VerifyLicenseDir.
MSI (c) (4C:E8) [13:21:11:500]: Invoking remote custom action. DLL:
C:\... Entrypoint: VerifyLicenseDir
MSI (c) (4C:A4) [13:21:11:500]: Cloaking enabled.
MSI (c) (4C:A4) [13:21:11:500]: Attempting to enable all disabled
priveleges before calling Install on Server
MSI (c) (4C:A4) [13:21:11:500]: Connected to service for CA interface.
MSI (c) (4C!C0) [13:21:11:625]: PROPERTY CHANGE: Modifying NIDPATH
property. ...
MSI (c) (4C!C0) [13:21:11:625]: PROPERTY CHANGE: Modifying FIDPATH
property. ...
Action ended 13:21:11: VerifyLicenseDir. Return value 1.
Any thoughts?
From: [EMAIL PROTECTED]
[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 everything correctly though, and I get a ton
of errors in wcautil.h, like
E:\Program Files\WiX\sdk\inc\wcautil.h(48): error C2065: '__in' :
undeclared identifier
And
E:\Program Files\WiX\sdk\inc\wcautil.h(48): error C2182:
'WcaGlobalInitialize' : illegal use of type 'void'
I've tried to include dutil.lib and wcautil.lib. Is there something
else that needs to be configured to use wcautil.lib (specifically
WcaLog)?
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
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 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 everything
missing myself (to /**/ ).
I read that they might be defined by default in VS05, but not in
VS03 (what I'm using.)
However, I rebuilt my installer with the new DLL and ran it with
*cv logging, and I still don't see anything.
The CA call seems to execute properly in all other regards.
I put a WcaLog statement as the first line in my method.
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
Here's the section of log where I expected to see some output.
MSI (c) (4C:98) [13:21:11:484]: Doing action: VerifyLicenseDir
MSI (c) (4C:98) [13:21:11:484]: Note: 1: 2205 2: 3: ActionText
Action 13:21:11: VerifyLicenseDir.
Action start 13:21:11: VerifyLicenseDir.
MSI (c) (4C:E8) [13:21:11:500]: Invoking remote custom action.
DLL: C:\... Entrypoint: VerifyLicenseDir
MSI (c) (4C:A4) [13:21:11:500]: Cloaking enabled.
MSI (c) (4C:A4) [13:21:11:500]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (4C:A4) [13:21:11:500]: Connected to service for CA
interface.
MSI (c) (4C!C0) [13:21:11:625]: PROPERTY CHANGE: Modifying
NIDPATH property. ...
MSI (c) (4C!C0) [13:21:11:625]: PROPERTY CHANGE: Modifying
FIDPATH property. ...
Action ended 13:21:11: VerifyLicenseDir. Return value 1.
Any thoughts?
From: [EMAIL PROTECTED]
[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 everything correctly though, and I
get a ton of errors in wcautil.h, like
E:\Program Files\WiX\sdk\inc\wcautil.h(48): error C2065: '__in'
: undeclared identifier
And
E:\Program Files\WiX\sdk\inc\wcautil.h(48): error C2182:
'WcaGlobalInitialize' : illegal use of type 'void'
I've tried to include dutil.lib and wcautil.lib. Is there
something else that needs to be configured to use wcautil.lib
(specifically WcaLog)?
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
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 have just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action: VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3: ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom action. DLL:
C:\... Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all disabled
priveleges before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for CA interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was guessing it was just
going to be used as an identifier in the log output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize 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: [WiX-users] Logging in a custom action
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 Simonea
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
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]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 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 have
just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action: VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3: ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom action.
DLL: C:\... Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for CA
interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was guessing it
was just going to be used as an identifier in the log output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize 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: [WiX-users] Logging in a custom action
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 Simonea
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
It's an immediate CA. I tried wrapping my strings with _T() but _T is
not defined. Another VS05 difference?
Could my definitions be causing a problem? I more or less copied them
from a forum post I saw regarding a similar problem.
#define __out /* ? */
#define __in /* ? */
#define __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 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 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 have
just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action: VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3: ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom action.
DLL: C:\... Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for CA
interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was guessing it
was just going to be used as an identifier in the log output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize 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: [WiX-users] Logging in a custom action
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 Simonea
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
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 Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[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 defined. Another VS05 difference?
Could my definitions be causing a problem? I more or less copied
them from a forum post I saw regarding a similar problem.
#define __out /* ? */
#define __in /* ? */
#define __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 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 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
have just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE
hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action:
VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3:
ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom
action. DLL: C:\... Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for
CA interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was
guessing it was just going to be used as an identifier in the log
output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize
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: [WiX-users] Logging in a custom action
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 Simonea
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
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 only I could log what was going on
Assuming the lack of wrapping my strings was not the issue, is there
anything else (no matter how obvious, cause it might not be obvious to
me) that I might be doing wrong?
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 3:18 PM
To: Rowland, Chris; 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.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[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 defined. Another VS05 difference?
Could my definitions be causing a problem? I more or less copied
them from a forum post I saw regarding a similar problem.
#define __out /* ? */
#define __in /* ? */
#define __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 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 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
have just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE
hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action:
VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3:
ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom
action. DLL: C:\... Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all
disabled priveleges before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for
CA interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was
guessing it was just going to be used as an identifier in the log
output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize
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: [WiX-users] Logging in a custom action
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 Simonea
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users
Re: [WiX-users] Logging in a custom action
Yeah, the error was in the custom action. (It returned the value 3)
I had tried to attach to msiexec.exe before to debug, but didn't make
any progress with that.
Can you show me how you fired off the MessageBox from within your CA?
This is a lot of debugging just so I can 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 you can always
try to debug the custom action in Visual Studio. I was able to do this
by adding a MessageBox to the beginning of the custom action and then
attaching to the MessageBox when the custom action was run. If the
error was when 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: 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 only I could log what was going on
Assuming the lack of wrapping my strings was not the issue, is
there anything else (no matter how obvious, cause it might not be
obvious to me) that I might be doing wrong?
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 3:18 PM
To: Rowland, Chris; 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.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[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 defined. Another VS05 difference?
Could my definitions be causing a problem? I more or
less copied them from a forum post I saw regarding a similar problem.
#define __out /* ? */
#define __in /* ? */
#define __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 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 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 have just:
extern C UINT __stdcall
VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall,
VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter
VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action:
VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2:
3: ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote
custom action. DLL: C:\... Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking
enabled.
MSI (c) (04:C0) [14:19:38
Re: [WiX-users] Logging in a custom action
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 -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 the custom action. (It returned the value 3) I had tried to attach to msiexec.exe before to debug, but didn't make any progress with that. Can you show me how you fired off the MessageBox from within your CA? This is a lot of debugging just so I can 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 you can always try to debug the custom action in Visual Studio. I was able to do this by adding a MessageBox to the beginning of the custom action and then attaching to the MessageBox when the custom action was run. If the error was when 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: 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 only I could log what was going on Assuming the lack of wrapping my strings was not the issue, is there anything else (no matter how obvious, cause it might not be obvious to me) that I might be doing wrong? From: Brian Simoneau [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 3:18 PM To: Rowland, Chris; 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. -Brian Simoneau -Original Message- From: [EMAIL PROTECTED] [mailto:[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 defined. Another VS05 difference? Could my definitions be causing a problem? I more or less copied them from a forum post I saw regarding a similar problem. #define __out /* ? */ #define __in /* ? */ #define __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 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 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
Re: [WiX-users] Logging in a custom action
Have you tried the MSIBREAK env var? It might be superior for what your
doing if your end goal isn't production logging here.
That is if you're only trying to get extra logging working to debug
something vs logging for normal operation.
Note that if it's a C++ CA you'll need 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
Yeah, the error was in the custom action. (It returned the value 3)
I had tried to attach to msiexec.exe before to debug, but didn't make
any progress with that.
Can you show me how you fired off the MessageBox from within your CA?
This is a lot of debugging just so I can 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 you can always
try to debug the custom action in Visual Studio. I was able to do this
by adding a MessageBox to the beginning of the custom action and then
attaching to the MessageBox when the custom action was run. If the
error was when 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: 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 only I could log what was going on
Assuming the lack of wrapping my strings was not the issue, is
there anything else (no matter how obvious, cause it might not be
obvious to me) that I might be doing wrong?
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 3:18 PM
To: Rowland, Chris; 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.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[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 defined. Another VS05 difference?
Could my definitions be causing a problem? I more or
less copied them from a forum post I saw regarding a similar problem.
#define __out /* ? */
#define __in /* ? */
#define __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 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 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 have just:
extern C UINT __stdcall
VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall,
VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter
VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS
Re: [WiX-users] Logging in a custom action
You don't want to use _T() because that would switch your strings to UNICODE if
you build Unicode and the WcaLog expects char for the first string.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Simoneau
Sent: Thursday, April 26, 2007 11:59 AM
To: [EMAIL PROTECTED]; 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] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 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 have just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action: VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3: ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom action. DLL: C:\...
Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for CA interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was guessing it was just going
to be used as an identifier in the log output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize 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: [WiX-users] Logging in a custom action
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 Simonea
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
I believe the latest Platform SDK defaults the sal.h in to windows.h now.
We're using the latest Platform SDK so that should just be available right away.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Simoneau
Sent: Thursday, April 26, 2007 12:18 PM
To: [EMAIL PROTECTED]; 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.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED] [mailto:[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
defined. Another VS05 difference?
Could my definitions be causing a problem? I more or less copied them from a
forum post I saw regarding a similar problem.
#define __out /* ? */
#define __in /* ? */
#define __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 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 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 have just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action: VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3: ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom action. DLL: C:\...
Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for CA interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was guessing it was just going
to be used as an identifier in the log output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize 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: [WiX-users] Logging in a custom action
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 Simonea
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
Are you dynamically linking against MSVCRT? More specifically, what are the
dependencies your CustomAction has on the OS and are they all met? It is
possible your CustomAction has some dependency and failing to load right off
the bat. Also, can you share the .wxs authoring for the 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 action. (It returned the value 3)
I had tried to attach to msiexec.exe before to debug, but didn't make any
progress with that.
Can you show me how you fired off the MessageBox from within your CA?
This is a lot of debugging just so I can 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 you can always try to
debug the custom action in Visual Studio. I was able to do this by adding a
MessageBox to the beginning of the custom action and then attaching to the
MessageBox when the custom action was run. If the error was when 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: 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 only I could log what was going on
Assuming the lack of wrapping my strings was not the issue, is there anything
else (no matter how obvious, cause it might not be obvious to me) that I might
be doing wrong?
From: Brian Simoneau [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 3:18 PM
To: Rowland, Chris; 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.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED] [mailto:[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
defined. Another VS05 difference?
Could my definitions be causing a problem? I more or less copied them from a
forum post I saw regarding a similar problem.
#define __out /* ? */
#define __in /* ? */
#define __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 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 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 have just:
extern C UINT __stdcall VerifyLicenseDir(MSIHANDLE hInstall)
{
WcaInitialize(hInstall, VerifyLicenseDir);
WcaLog(LOGMSG_STANDARD, Enter VerifyLicenseDir);
return WcaFinalize(ERROR_SUCCESS);
}
MSI (c) (04:F4) [14:19:38:375]: Doing action: VerifyLicenseDir
MSI (c) (04:F4) [14:19:38:375]: Note: 1: 2205 2: 3: ActionText
Action 14:19:38: VerifyLicenseDir.
Action start 14:19:38: VerifyLicenseDir.
MSI (c) (04:C8) [14:19:38:390]: Invoking remote custom action. DLL: C:\...
Entrypoint: VerifyLicenseDir
MSI (c) (04:C0) [14:19:38:390]: Cloaking enabled.
MSI (c) (04:C0) [14:19:38:390]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (04:C0) [14:19:38:390]: Connected to service for CA interface.
Action ended 14:19:38: VerifyLicenseDir. Return value 1.
Did I feed WcaInitialize a bad 2nd argument? I was guessing it was just going
to be used as an identifier in the log output.
Do I need to call WcaGlobalInitialize/WcaGlobalFinalize in some way as well?
Thanks again for your help. Google doesn't reveal much on this subject :(
From: Brian Simoneau
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 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: Wednesday, April 25, 2007 4:08 PM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] Logging in a custom action Is there any way to write a message to the install log from a custom action? Chris Rowland* Software Engineer * SunGard * Data Management Solutions * 1194 Oak Valley Drive, Suite 100 * Ann Arbor, MI 48108 * Tel 734.332.4423 * Fax 734.332.4440 * http://www.sungard.com/datamanagementsolutions http://www.sungard.com/datamanagementsolutions - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
::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.net Subject: [WiX-users] Logging in a custom action Is there any way to write a message to the install log from a custom action? Chris Rowland* Software Engineer * SunGard * Data Management Solutions * 1194 Oak Valley Drive, Suite 100 * Ann Arbor, MI 48108 * Tel 734.332.4423 * Fax 734.332.4440 * http://www.sungard.com/datamanagementsolutions - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
Note huge caveat that ::MsiProcessMessage() doesn't work from DoAction so if your CA is triggered by a button that will not work for logging. Not sure how you're supposed to log from these, I have not found a solution, perhaps someone else has Haven't used WcaProcessMessage so 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] Logging in a custom action ::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.net Subject: [WiX-users] Logging in a custom action Is there any way to write a message to the install log from a custom action? Chris Rowland* Software Engineer * SunGard * Data Management Solutions * 1194 Oak Valley Drive, Suite 100 * Ann Arbor, MI 48108 * Tel 734.332.4423 * Fax 734.332.4440 * http://www.sungard.com/datamanagementsolutions http://www.sungard.com/datamanagementsolutions __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging in a custom action
Correct, as you note, you cannot log from a DoAction launched CA. WcaProcessMessage is just a wrapper around MsiProcessMessage() that mostly adds handling for cancel. WcaLog() is a wrapper around WcaProcessMessage() that adds the concept of logging levels inside your own code and 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 ::MsiProcessMessage() doesn't work from DoAction so if your CA is triggered by a button that will not work for logging. Not sure how you're supposed to log from these, I have not found a solution, perhaps someone else has Haven't used WcaProcessMessage so 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] Logging in a custom action ::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.net Subject: [WiX-users] Logging in a custom action Is there any way to write a message to the install log from a custom action? Chris Rowland* Software Engineer * SunGard * Data Management Solutions * 1194 Oak Valley Drive, Suite 100 * Ann Arbor, MI 48108 * Tel 734.332.4423 * Fax 734.332.4440 * http://www.sungard.com/datamanagementsolutions __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] logging of RemoveExistingProducts
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. As far as your logging question goes, you should be able to see those actions (if they are in fact included) and the other stuff that is happening when the cached msi is removed by using l*v. Ok, thanks (also to Stefan Krueger). A typical example of PEBKAC: The condition of the custom action was wrong. I see the deinstallation now as expected. Andre' - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] logging of RemoveExistingProducts
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
side actions.
--
Stefan Krueger
Microsoft Windows Installer MVP
Please post your questions in the newsgroup or vist one of these web sites:
Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de
InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)
André Pönitz [EMAIL PROTECTED] schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
I have a product that needs to run custom actions
when uninstalling. This works.
However, when trying to install a major upgrade
on an already installed version the older version
is properly found (i.e. I get something like
MSI (s) (3C:DC) [09:51:36:582]: PROPERTY CHANGE:
Adding NEWERVERSIONDETECTED property.
Its value is '{7F141428-1AC6-46F5-9915-763C2F1D5F11}'.
in the log) but it looks as if during its
deinstallation the custom actions do not run.
Ordinary deinstallation works just fine.
Is there a way to see the stuff that happens
when 'RemoveExistingProducts' somehow in the log
file (I am using /l*v already)
Andre'
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
