Hi, I have a .Net assembly file with file version "4.0.763.0" and assembly version "4.0.0.0". In order to install it into the GAC I have used latest Wix3 toolset and faced a wrong registration issue. Taking a look into the MSI file with Orca tool shows that in MsiAssemblyName table the file version is as expected "4.0.763.0" however the version is "4.0.0.000" (with two redundant zeros). I would not mind it if I was not using the "bind" feature of the "light" for creating registry keys for COM registration. It all worked fine when file version and assembly version were the same number. Oddly enough when assembly version has less meaningful digits, "light" adds zeros to have both versions with the same number of digits. Am I the only one to face this problem? How do others register .Net assemblies? Do you always use the same numbers for file version and assembly?
Thanks, Dov ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
