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.
Results that may be inaccessible to you are currently showing.
Hide inaccessible results
Feedback