Yes. DTF runs each managed custom action in its own dedicated process. Because the process is separate and new, there is no risk of some other CLR version already being loaded into it. Only an unmanaged stub runs in the MSI custom action server process -- that stub coordinates the launch of the new process for managed code and the communication with it.
-Jason- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Buddell, James Sent: Friday, August 08, 2008 5:43 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] DTF and .NET Framework on Windows Server 2003 http://robmensching.com/blog/archive/2007/04/19.aspx The above blog tells us that one of the reasons not to use managed code for DLL CAs is because .NET Framework version 1.1 is always loaded on Windows Server 2003 regardless of the code's required .NET version. I know that DTF addresses the sticky CLR problem, but can find no mention of this second problem. Does DTF resolve this issue? If it's been fixed separately in a Windows Server 2003 update then please could someone supply the reference so that I can check that we have the fix deployed. Thanks, James ------------------------------------------------------------------------- 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
