We could get rid of the CRT dependencies and I used to do that work (had to
port over sprint to do it too, that was a pain). However, the new CRT has a
lot of really nice security checks built-in that I don't want to try to port
over. So, we static link the CRT now to get those security features because
dynamic linking is just suicide. In fact, based on the (IMHO) failure that is
Win32 SxS I think it is probably really dangerous to use the CRT DLLs.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, December 06, 2006 21:33
To: Mike Dimmick
Cc: [email protected]; 'Matthew Kowalski'
Subject: Re: [WiX-users] VS2005 C++ and Custom Actions
Mike Dimmick wrote:
You should try to eliminate use of the CRT, if possible, and statically link
with it to remove the dependency on the CRT DLLs.
There's nothing wrong with using the CRT as long as you statically link.
The WiX custom actions should probably take the lead here and replace calls to
CRT functions with equivalent Windows functions, then replace the CRT-supplied
entry point function with a stub. This could well reduce the size of the custom
action DLLs.
Why? Unless we got rid of CRT dependencies entirely...
--
sig://boB
http://bobs.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
