\nIt turns out that you can force SQL Server to use FX libraries that are not on the approved list. Deploying user code that uses these through Visual Studio produces:\n<\/p>\n
\nError: Assembly 'system.runtime.remoting, version=2.0.3600.0, culture=neutral, publickeytoken=b77a5c561934e089.' was not found in the SQL catalog.\n<\/p>\n
\nBut that's because Visual Studio uses CREATE ASSEMBLY "from bytes", passing in the byte array. You can also use "CREATE ASSEMBLY foo FROM 'c:\\types\\foo.dll'. SQL Server then searches the directory specified (c:\\types in this case) for dependent assemblies. When you use VS autodeploy it doesn't do this, making "automatic cataloging of dependent assemblies with IsVisable=No" difficult (impossible?) to prove when using autodeploy.\n<\/p>\n
\nWhen I use CREATE ASSEMBLY with a file on my "simple remoting program", there is a more telling error:\n<\/p>\n
\nMsg 6581, Level 16, State 1, Line 1
\nCould not find assembly 'system.runtime.remoting' in directory 'c:\\types\\'.\n<\/p>\n
\nOh. Copying 'System.Runtime.Remoting' to c:\\types produces another "Could not find assembly". Eventually I put my assembly in the FX lib directory so it can resolve everything and set the permission_set to unsafe. This works and I've deployed it. Looking in sys.assemblies, it's taken 15 FX libraries that are not on "the list" with it. They're cataloged as "normal" libraries with IsVisible=True in the metadata. That means you can't declare catalog or use their methods from SQL Server directly, only from other user assemblies, subject (of course) to security.\n<\/p>\n
\nIt also DOESN'T imply that these libraries are unsafe in general, just when you use SQL Server as a runtime host. SQL Server likes to do things like control it's own threading, exception handling, memory allocation, etc, etc. Most\/all other current runtime hosts don't. It's not going to USE most\/any of these in my one-line program, mind you, it's just following dependency chains in the manifests. Things may work fine.\n<\/p>\n
\nBTW, just in case you didn't gather this, this is NOT NOT NOT RECOMMENDED. Just meant to answer the question "can you…". I, for one, am GLAD there's a list. That they are definately looking out for reliability\/scalability\/etc. Very cool.<\/p>\n","protected":false},"excerpt":{"rendered":"
It turns out that you can force SQL Server to use FX libraries that are not on the approved list. Deploying user code that uses these through Visual Studio produces: Error: Assembly 'system.runtime.remoting, version=2.0.3600.0, culture=neutral, publickeytoken=b77a5c561934e089.' was not found in the SQL catalog. But that's because Visual Studio uses CREATE ASSEMBLY "from bytes", passing in […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28,38],"tags":[],"class_list":["post-1021","post","type-post","status-publish","format-standard","hentry","category-sql-server-2005","category-sqlclr"],"yoast_head":"\n