Niels SQL Server Blog

In an earlier post I wrote how I had created a custom MSBuild task to deploy CLR assemblies to Yukon. It turned it was more useful than I first had thought (with automatic deployment in VS.NET and all). First, I do not always use VS.NET (Emacs is a great editor), and secondly even when I use VS.NET the deployment feature is a bit shakey.

So a while ago I decided to enhance the task a bit (among other thngs it didn't do cataloging of procedures etc based on the methods in the assembly. Some of the new features are:

• Cataloging of procedures, UDF's and triggers based on the methods in the assembly.
• This can be done by the task by inferral based on the return value of the CLR methods. Void and integer creates procs, everything else creates functions. Triggers can not be created this way.
• If not using inferral the developer can define what a methos should be created as by using attributes. There are custom attributes for Procedures, Triggers and Functions. There is also an attribute to define size of parameters and return values.
• In addition to deploying the assembly and its methods to the database the task can also output a script file with the T-SQL syntax fro the deployment. The developer can choose to either just deploy witn no file, deploy with file or just create the file and no deployment.

The code, binaries and documentation can e downloaded from here (about 66k). Have fun and comments are always welcome!!