Archive for January, 2008

Update of SQLCLRProject

January 30, 2008

I’ve had some feed-back about SQLCLRProject (thanks Doug et al!), and based on that fixed some issues.

Read all about it, and get the updates on the download page.

As always, comments and suggestions for improvements are very welcome!!

Niels

Advertisements

Like Phoenix Rising … or New Version of SQLCLRProject

January 14, 2008

Hi everyone, it’s been a while šŸ™‚ (shame one me!)!!

As some of you may know, back in the days I developed a tool for deploying .NET assemblies to SQL Server 2005 (or, as it was called then, Yukon). Initially it was just a tool used from the command line. As time went by, it evolved into a project named SQLCLRProject, consisting of the command line tool (YukonDeploy), a stand-alone front-end GUI, DeployProperties, and an add-in (with project and item-templates) for Visual Studio, DeployAddIn.

The latest release of SQLCLRProject was back in February 2006 (wow, that was a long time ago šŸ˜¦ ) , and up until a month or so, nothing much was done to it. I used it whenever I did any SQLCLR work and I know other developers were using it as well. Anyway, a while back I started receiving emails from people wondering if I could fix some “undocumented features” and/or implement some new features.

So, I decided to resurrect the project and the last weeks I have been working on fixing the issues and adding some more features. I’m fairly happy with it as it is right now, and today I release version 2.5. The download page for it is here.

So what has been done:

  • The project has now it’s own web-pages, so I have a place to point people to when explaining what SQLCLRProject is.
  • The Visual Studio add-in (and templates) supports both VS 2005 as well as VS 2008
  • The VS add-in (as well as the other tools) supports both SQL Server 2005 as well as SQL Server 2008 (Katmai).
  • The previous version of the tool allowed you to re-deploy a UDT without manually dropping tables with columns based on the UDT. The tool either dropped the whole table or just the column (based on a configurable setting), before re-deploying. In this version the choice is as before to either to drop the whole table or the column. However if choosing to drop the column:
    • first the table is altered and a new column is added (varchar(max) or varbinary(max) – also based on a configurable setting),
    • then the data from the original column is copied over to the new column
    • finally the original column is dropped.
  • In T-SQL we have the notion of procedure parameters with default values. In .NET we don’t have anything similar (well, VB.NET has optional parameters, but that is a compiler hack). The tool now allows you to, by using an attribute, defining parameters in your .NET code that will be created as T-SQL object with default values.
  • Fixed a bug where the add-in for VS could not handle project with white spaces in the path.

So, if you are interested, go to here to read more about SQLCLRProject and if you want to download; the download page is here.

Comments etc are always welcome, post a comment here (or on the main page) or drop me an email.

Niels