1. Dark can convert an existing MSI into .wxs files. You may be able to use the "-f" switch to highly fragment everything and use the output as-is. It sounds like there is just a lot of registration that is necessary for these assemblies.
2. If you can, please file detailed bugs on heat.exe if it is missing things. It isn't like we know anything more about .NET Assemblies and TypeLibs than you do. We aren't skipping important registration on purpose. <smile/> -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 13:47 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Ongoing problems Hello again, I've been tearing my hair out over the last week trying (but failing) to register a .Net assembly & TypeLib in WiX 3 (so apologies if I sound frustrated). Heat only got half way - and even then I had to alter the output somewhat in order to get it to do the equivalent registry entries. However, this still failed to do the registration correctly. My reading around WiX registration of assemblies seems to suggest there's no easy solution to this (otherwise I'm sure I would have found it by now). If there is anyone out there that has succeeded in such a .net registration - please can you let me know what you did in order to get it to work. Anyway - the long and short of it is that as a short-term fix we've had to produce a Visual Studio 2008 setup project just to install the assembly and tlb file - and run this after the install of our WiX based product installer. Obviously this isn't ideal - but we cannot ship our product with a broken assembly registration (and we are unable to register it manually even using regasm /codebase /tlb). One thing that I do have now, is a complete .msi file that I can investigate to try and work out what's different between the WiX attempt at registration and a known working one. I've taken a brief look in orca - but was put off by the sheer number of things to check. My question is - how should I go about getting the know working parts from the working .MSI into WiX? Should I do it table-by-table? There are literally thousands of registry entries - so it could take a while. I'm happy to post any details that are required - or indeed the assembly itself if that would help. It's unfortunate that this has been a stumbling block - as I've been singing the praises of WiX having previously jettisoned the dreadful InstallShield. Thank you, Ben. ------------------------------------------------------------------------- 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=100&url=/ _______________________________________________ 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=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
