• shibbard 51721 (6/28/2016)


    I am totally excited to find this great series, I need to get up to speed quickly on CLR and the security issues involved and your tutorial is exactly what I was looking for. I really appreciate the detailed, step-by-step instructions with explanations of ‘why’ things are done, as well.

    Hi there. Thank you very much for that compliment. I very much appreciate hearing that you appreciate the detail that I put into these articles. It takes quite a bit of time and energy (hence why I am not done with the series yet) but I think it's all worth it if it increases the general level of understanding of SQLCLR among the community, such that people are more successful using it and use it more appropriately.

    To learn by doing, I’ve gone through the steps in Part 6 and 7 – but I’m running into an issue however – it looks like the SQL query for AssemblySecuritySetup-Part1of2.sql might be truncated? When I paste it into either MSVS editor, or SSMS, it is getting flagged by Intellisense with the error ‘Unclosed quotation mark after the character N’ (line 55) and ‘Incorrect syntax near end of file’ at the very end.

    That script is the first half (hence named "Part1of2") of what will get concatenated into a single SQL script, along with "Part2of2" and a fragment of a file that gets produced when you compile the Assembly (so it doesn't exist yet). So yes, those Intellisense errors are to be expected. At this point, all you need to do is save the script so that it exists to be concatenated in the PostBuild Event.

    Please let me know if that does not work, or if you have additional questions.

    Take care,

    Solomon..

    SQL#https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
    Sql Quantum Lifthttps://SqlQuantumLift.com/ ( company )
    Sql Quantum Leaphttps://SqlQuantumLeap.com/ ( blog )
    Info sitesCollations     •     Module Signing     •     SQLCLR