On Wed, 8 Sep 2010 14:21:58 +0200 Tobias S <tobias.s1...@gmail.com> wrote:
> For the older versions of the Framework I always used the reg > detection mechanism which was also the Microsoft recommended way > (Sorry don't know the MSDN reference at the moment). InstallShield > also uses the reg detection for 4.0 versions: > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework > Setup\NDP\v4\Client Install = 1 > for client profile and for full one > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full > Install = 1 I don't think I've seen any documentation from Microsoft about using the version of mscoree.dll but got the idea from a previous thread on wix-users. Since I expect to be updating the application regularly I'll switch back to using registry detection: it won't become an issue for a few years. > Think here the problem is that you don't know what is the policy used > by Microsoft for compatibility of the managed components with newer > framework versions. So for example 2.0 components may also work with > 4.0 Framework (where no 2.0 Framework is present - somehow a bit > seldom but possible with XP SP3). So in my oppinion for the 4.0 > Framework should detect exactly version 4.0 to ensure compatibility of > the application with the framework it was tested with. http://msdn.microsoft.com/en-us/library/ff602939.aspx explains the policy for backwards compatibility. I remember I had problems deserialising data created with .NET 1.1 on a system with 1.1SP1 so I'm not sure how far I'd trust it with anything more complex than a console application. -- Bruce Cran ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
