No, you can't do it. The CLR uses TLS in various ways that don't play nicely with SQL Server. .NETFX 2 and Yukon have both undergone significant work to resolve this issue.
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback