Thanks for the reply. But what if the dll is a .net dll? You know in .net one assembly can have reference to another .net assembly; can the same functionality be done for a SQLCRL assembly?
Hi there. I will cover this concept in a future article (or 2), but the simple answer is "Yes" and it is the same in all versions of SQL Server since SQLCLR was introduced in SQL 2005.
The more complicated answer is: as usual, you need to add a reference to the DLL in your project. Now, if the DLL is a .Net framework DLL, then not all of them are natively available in SQL Server's restricted CLR. There is a list of which ones are valid and it is a rather short list. You can still use non-validated framework DLLs, but you need to import them into SQL Server in the manner shown by "currentp" and that can only be done if they are marked as UNSAFE. Does this answer the question?
-- Solomon Rutzky - I hope I'm not stealing your thunder 🙂
Nope, not at all. Anyone is welcome to answer questions :-).