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 > ------------------------------------------------------------------------------ > 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
