SQL Server 2008 and the upcoming SQL Server 2008 R2 Edition, formerly codenamed "Kilimanjaro," will both continue to download the latest CLR version 2.0 release service.
You might be wondering what is the rationale for supporting SQL Server to download version 2.0 of the CLR? This is just a healthy, cautious attitude, existing UDT, UDA, etc. are not broken; or is it because additional engineering support for the new CLR?
It seems that the answer is actually not enough of both.
Now with the .NET Framework 4.0, we now have the ability to download two or more separate versions of the CLR within a single process. In previous releases of the .net infrastructure, a process can only load one instance of the CLR. Given this limitation, the CLR team recommended that hosts such as SQL Server use the LockClrVersion function to determine the version of the CLR to load before initialization. So, as stated earlier, SQL Server 2008 and SQL Server 2008 R2 will continue to download the latest release of the CLR version 2.0 service, since the version is locked until the CLR initialization begins.
In future versions, SQL Server may load newer versions of the CLR or even support loading multiple CLRs in the process, CLR version 2.0 is here to stay in SQLCLR in SQL Server 2008 and SQL Server 2008 R2.