We have a working clr proc in SQL Server 2008 r2. We are trying to migrate to 2012. All .net 2 assemblies fail creation but the same assemblies are created when version 4. The clr is custom assembly that calls a 3rd party assembly (.NET xPorter for Excel) which specifies some .NET 2 libraries.
The .net 2 SDK is installed, the database is set to trustworthy, the users are sa, KB2742595 was applied last month.
An example follows, note the exact same warning comes up for both only the .net 2 fails ....
DROP assembly [System.Drawing]
GO
create assembly [System.Drawing]
from 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll'
WITH PERMISSION_SET = UNSAFE
GO
--Warning: The Microsoft .NET Framework assembly 'system.drawing, version=2.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
--Msg 6586, Level 16, State 1, Line 1
--Assembly 'System.Drawing' could not be installed because existing policy would keep it from being used.
create assembly [System.Drawing]
from 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Drawing.dll'
WITH PERMISSION_SET = UNSAFE
GO
--Warning: The Microsoft .NET Framework assembly 'system.drawing, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
Thanks,
Leif Peterson