you don't. there is a key (strong name) and user defined per assembly. this is how clr permissions are defined.
note: the key is defined in the signed assembly.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi All,
Trying to work on CLR objects. I have created dll from Visual studio using strong name.
Now I need to create assembly for that new file. We already have CLR implemented for another dll.
I want to use same assymetric key and user to create assembly and CLR SPs. I want to do this because key and user are already set up to be external_access and plumbing is done.
I am not seeing any articles or resources that tells how to use existing asymmetric key for multiple dlls.
Any help is appreciated.
Thank You
you don't. there is a key (strong name) and user defined per assembly. this is how clr permissions are defined.
note: the key is defined in the signed assembly.
Hi @Spunny
Not an expert of SQL CLR, but hope this article will help: Impact of CLR Strict Security configuration setting in SQL Server 2017
Best regards,
Cosmog Hong
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.