This vbscript will report all components on the system and what products have
them as clients.
=================================================
Option Explicit
Public installer, fullmsg, comp, a, prod, fso, pname, ploc, pid, psorce
Set fso = CreateObject("Scripting.FileSystemObject")
Set a = fso.CreateTextFile("comps.txt", True)
' Connect to Windows Installer object
Set installer = CreateObject("WindowsInstaller.Installer")
a.writeline ("MSI Components")
on error resume next
For Each comp In installer.components
a.writeline (comp & " is used by the product:")
for each prod in Installer.ComponentClients (comp)
pid = installer.componentpath (prod, comp)
pname = installer.productinfo (prod, "InstalledProductName")
a.Writeline (" " & pname & " " & prod & "and is installed at " & pid)
Next
Next
==========================================================
Phil Wilson
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Butcher
Sent: Friday, March 28, 2008 2:43 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] ServiceInstall and ServiceControl
Thanks Bob
I've done a registry search for the GUIDs used in the WXS file, but no entries
in the registry.
How would you suggest exploring where the component is shared, or how do you
identify component rules violations?
Krs
Chris
________________________________
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 27 March 2008 14:38
To: Christopher Butcher
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] ServiceInstall and ServiceControl
Christopher Butcher wrote:
The service does uninstall, the files are deleted by the MSI ok. It's just that
whatever registry entries which enable the service to appear in SERVICES.MSC
are left in place. If I delete them manually and then reboot then the service
is removed from SERVICES.MSC. But surely you shouldn't need to do that. I have
seen MSI's gracefully remove services completely - why would this one be acting
so ungraceful?
Action start 21:01:24: InstallValidate.
MSI (s) (CC:1C) [21:01:24:890]: Feature: DefaultFeature; Installed: Local;
Request: Absent; Action: Absent
MSI (s) (CC:1C) [21:01:24:890]: Component: C_SERVICEEXE; Installed: Local;
Request: Absent; Action: FileAbsent
The FileAbsent action indicates that the component is shared with another
product installed in a different directory. If that's not the case, you likely
have a component rules violation between different products over time.
--
sig://boB
http://joyofsetup.com/
Disclaimer of IDOX Group plc ("IDOX")
This e-mail and any attachments are confidential, may be privileged and are
intended solely for the use of the intended recipient/s. If you are not an
intended recipient, please (a) notify the sender immediately, copying [EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]> as appropriate; and (b) delete the
original e-mail and your reply from your system. Unless authorized by IDOX,
copying, forwarding, disclosing or using this e-mail is prohibited. No
liability is accepted for damage caused by the presence of any virus. The
contents of this e-mail are provided "subject to contract". Views or opinions
in this e-mail are those of the author and not necessarily those of IDOX . IDOX
may intercept, copy or monitor e-mails from or to anyone using its facilities
in accordance with the law.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
