I'm porting a .NET product from and older InstallShield to WiX. My ignorance of details of MSI and .NET's interactions with the registry are showing through here.
I used heat to do the heavy lifting, and all files are in the correct place after install. However, I can't get the WiX-installed application to do anything but crash out of the gate. In diff'ing the registry exports of the two installs, I see entries like the following in the old IS install, but not the WiX install. (Names change to protect the guilty. *grin*) [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Assemblies\C:|Program Files|ACME|FooProject|Foo.Runtime.dll] "Foo.Runtime,Version=\"3.1.0.38471\",Culture=\"neutral\",ProcessorArchitecture=\"MSIL\",PublicKeyToken=\"1234567890123456\""=hex(7):28,\ 00,75,00,33,00,5d,00,67,00,5b,00,70,00,48,00,38,00,3d,00,5b,00,4c,00,57,00,\ 00,00,6d,00,43,00,6c,00,3d,00,5a,00,72,00,3e,00,4a,00,66,00,6e,00,69,00,4d,\ 00,77,00,69,00,37,00,46,00,4e,00,52,00,21,00,47,00,40,00,21,00,44,00,7b,00,\ 00,00,45,00,40,00,00,00,00,00 Googling suggests that perhaps the WiX version is not creating private assembly entries in the registry, but I'm not seeing how to do this. Adding Assembly=".net" to the <File> tag is for strong name assemblies, which these are not. Or, if I'm barking up an obviously wrong tree, I'm open to correction too. :) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
