I don't think heat can do this but tallow from v2 can: tallow -reg file.reg file.wxs
The output should work ok in v3 (or WixCop will fix it). Neil From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pally Sandher Sent: 28 May 2008 18:53 To: wix-users@lists.sourceforge.net Subject: [WiX-users] converting .reg to .wxs in WiX 3.0 Hi, I'm using v3.0.4116.0 currently (installing v3.0.4123.0 first thing tomorrow morning). I have a problem with the COM registration info heat.exe generates for one of our executables (not written by me). It doesn't seem to get all the required entries. The generated code is as follows: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Fragment> <DirectoryRef Id="appsFolder"> <Component Id="iesoop" Guid="503CDCB9-669D-4c18-BF30-B1319A127326"> <File Id="iesoop.exe" Name="iesoop.exe" KeyPath="yes" Source="..\..\..\bin_release\iesoop.exe"> <TypeLib Id="{7749E01A-8723-476D-905F-E8F97EDF8AF6}" Description="iesoop Type Library" Language="0" MajorVersion="4" MinorVersion="0"> <Interface Id="{22624D71-96AA-4581-AF1B-E58539EB3EC3}" Name="_IBridgeEvents" ProxyStubClassId="{00020420-0000-0000-C000-000000000046}" ProxyStubClassId32="{00020420-0000-0000-C000-000000000046}" /> <Interface Id="{93B8BD76-7C0A-4119-84C7-3FDCF9B7477C}" Name="IBridge" ProxyStubClassId="{00020424-0000-0000-C000-000000000046}" ProxyStubClassId32="{00020424-0000-0000-C000-000000000046}" /> </TypeLib> </File> <RegistryValue Root="HKCR" Key="TypeLib\{7749E01A-8723-476D-905F-E8F97EDF8AF6}\4.0\HELPDIR" Value="[appsFolder]" Type="string" Action="write" /> </Component> </DirectoryRef> </Fragment> </Wix> When I use RegSpy on this app it generates much more than those entries above. When I install our application it fails to run. If I run the above executable after installation with the /regserver parameter then run our application it works fine. This is what leads me to believe heat.exe is missing some of the self-registration info. In WiX 2.0, tallow.exe happily took a .reg file & output the required XML, heat.exe in 3.0 refuses to play the game (outputs a fragment with a directory, component & file tag for the .reg file!). Does anyone know how I can convert the .reg file I've extracted using RegSpy to WiX 3.0 XML? heat.exe seems to have no documentation at all other than what it outputs when run with /? I really don't want to have to use a custom action for this. Cheers, <http://www.iesve.com/> Palbinder Sandher Software Deployment and IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com <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 <http://www.iesve.com/disclaimer.html>
<<image001.jpg>>
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
