Back in December I released a new version of SqlClrProject, it was
followed by an update in January. After the update I received some
functionality requests - being able to define the names of the
parameters that are being created. Some times, the names you want to
give to your procedure/function parameters may not be valid .NET param
names, so in those cases it can be useful to be able to explicitly
define the names.
Anyway, I have implemented that by defining a new custom attribute -
SqlParamFacetAttribute - which derives from SqlFacetAttribute. As this
new attribute is a custom attribute it has to be deployed to SqlServer
in its own dll. The deployment task is doing that automatically during
deployment if the attribute dll is not here already.
Here follows for you who don't know what the SqlClrProject is the
marketing blurb:
The SqlClrProject is a project type for Visual Studio 2005 for creation
and deployment of assemblies to SQL Server 2005. It consists of
templates for both Visual C# (C#) and Visual Basic (VB) with skeleton
code for creation of CLR methods to be used as stored procedures, User
Defined Functions (UDF's), triggers, User Defined Types (UDT's) and User
Defined Aggregates (UDA's). Some of the features are:
* Ability to deploy the assembly to SQL Server and create the SQL
Server methods, all from inside the Visual Studio IDE.
* Automatic creation of T-SQL deployment scripts.
* Automatic creation of T-SQL DML scripts for testing of the created
objects.
* Ability to alter an assembly and only deploy newly added methods
from the assembly.
* Ability to create objects in a non default schema
"schemaname.objectname".
* Debug facilities from inside VS.
For you who have used the SQL Server Project project type from VS to do
this, you may wonder what the differences are. Things that the
SqlClrProject allows you to do, which the VS SQL Server project can't
do:
* Automatic creation of T-SQL deployment scripts.
* Automatic creation of T-SQL DML scripts for testing of the created
objects.
* Ability to alter an assembly and only deploy newly added methods
from the assembly.
* Ability to create objects in a non default schema
"schemaname.objectname".
You can download it from here [0]. After download, unzip the zip file
and read the instructions for installation in the README.txt file.
Niels
[0]; http://staff.develop.com/nielsb/code/deploypropandaddin.zip
--
**************************************************
* Niels Berglund
* http://staff.develop.com/nielsb
* nielsb@no-spam.develop.com
* "A First Look at SQL Server 2005 for Developers"
* http://www.awprofessional.com/title/0321180593
**************************************************
|