I write a merge module that includes a local server MyProg.exe. This server has a lot of COM Classes that must be registered.
I know the method with RegSpy to generate a registry file and to harvest with "heat reg". This has the drawback that it generates each registry value as an indivual component. When I decompile the old InstallShield MSM I get structures using http://wix.sourceforge.net/manual-wix2/wix_xsd_class.htm like this <Component Id="" Guid=GUID SharedDllRefCount="yes"> <Class Id=GUID Context="LocalServer32" Description="Foo Class" AppId=GUID Advertise="yes"> <ProgId Id="My.Prog.1" Description="Prog Class" Advertise="yes" /> <ProgId Id="My.Prog" Description="Prog Class" Advertise="yes" /> </Class> <Class Id=GUID Context="LocalServer32" Description="Monitor Class" AppId=GUID Advertise="yes"> <ProgId Id="My.Monitor.1" Description="Monitor Class" Advertise="yes"> <ProgId Id="My.Monitor" Description="Monitor Class" Advertise="yes" /> </ProgId> </Class> <File Id="MyProg.exe" Name="MyProg.exe" KeyPath="yes" Vital="no" Compressed="yes" Source="SourceDir\File\MyProg.exe"> <TypeLib Id=GUID Advertise="yes" Cost="1" Description="MyProg 1.0 Type Library" HelpDirectory="MYPROG_INSTALL_DIR" Language="0" MajorVersion="256" MinorVersion="0" /> </File> </Component> Is there any method to get this kind of wxs source file from the local server or from the .reg file harvested with heat? Regards, Helge ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
