The VerQueryValueW() call has been there since WiX 3.5 forked from WiX 3.0, so I don't think this problem is necessarily Unicode-related. Perhaps you only recently started using FileUtil's FileVersion() function (which requires "version.lib" to be linked in)?
Try adding "version.lib" to the list of libs you link into your CA DLL. That may fix your problem. -----Original Message----- From: Albert At School [mailto:alb...@de-notenbalk.nl] Sent: Monday, April 26, 2010 1:29 AM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] WiX 3.5 dutil.lib build Hi, Why is there a sudden change in building the libs? In the wix-3.5.1623.0 the libs are build with Unicode while before they did not? I am compiling my CA DLLs (build in native C++) with non Unicode and after updating today to the build 1623 gives me the following link errors: 1>dutil.lib(fileutil.obj) : error LNK2001: unresolved external symbol _verqueryval...@16 1>dutil.lib(fileutil.obj) : error LNK2001: unresolved external symbol _getfileversionin...@16 1>dutil.lib(fileutil.obj) : error LNK2001: unresolved external symbol _getfileversioninfosi...@8 1>L:\Projects\bin\ReleaseStatic\vc90\Win32\_D4WMSI.dll : fatal error LNK1120: 3 unresolved externals While in previous versions there where no problems. If there was a change from Ansi to Unicode I might expect it to be noticed in the changes. Also, why not build/supply both libraries then? Regards, Albert van Peppen Senior System Engineer Insad Grafisch b.v. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
