What’s New and Download

This is where you find out the latest status of the SQLCLRProject and can download it from.

Download

Latest release:

Version File Name Download Comment
2.6 DeployPropAndAddIn_v2.6.zip Download from here Latest release, full install (~2.6 MB).

Earlier releases:

Version File Name Download Comment
2.5 DeployPropAndAddIn_v2.5c.zip Download from here Release 2.5, full install (~2.6 MB).
2.1 DeployPropAndAddIn_v2.1.zip Download from here
 Release 2.1, full install (~2 MB)
2.0 DeployPropAndAddIn_v2.0.zip Download from here
 Release 2.0, full install (~1.5 MB)

What’s New

February 27, 2008

Release of version 2.6

New features:

  • During deployment you’ll get a warning if you have dependencies on GAC:ed assemblies that are not in the “blessed” list.
  • There is now a setting where you indicate if you deploy against SQL Server 2005 or SQL Server 2008.

Fixes:

  • Debug symbols for referenced assemblies were not during deployment assigned to the respective referenced assembly, but to the main assembly. This meant you could not step into the code of a referenced assembly from the main assembly. This is now fixed.

January 30, 2008

Update of version 2.5

Fixes:

  • There were an issue with deploying referenced assemblies. If you had a complex assembly chain, the tool “missed” some referenced assemblies and you got an exception during deployment. This is hopefully fixed now.
  • Fixed so all debug symbol files are being deployed, i.e. even for referenced assemblies. Only the symbols file for the main assembly used to be deployed.

January 14, 2008

Release of version 2.5

New features:

  • Can define parameters in .NET code to have default values in T-SQL. This is done by using the SqlParamFacet attribute (see below).
  • Changed the behavior during re-deployment, so that instead of dropping a column and its data which is based on a UDT or CLR method, a new column is created (varchar or varbinary) and the data from the original column inserted into that temporary column before the original column is dropped.
  • Added a setting to control if you want to deploy the deployattributes.dll or not. (This assembly is needed if you are using the SqlParamFacet attribute).

Fixes:

  • Fixed a bug in the VS add-in, where if there was a whitespace in the path to the project, it could not be deployed.
  • Fixed an issue with dependent objects; if you had an independent T-SQL object (proc/function/etc) which called a CLR based object - the T-SQL object would be dropped during re-deployment. This does not happen any more.
  • The VS add-in had an issue where if you changed your connection-string on the add-in property page, you had to re-load the project before the change “took”.

February 8, 2006

Release of version 2.1

New features:

  • Created a new deployment attribute, SqlParamFacet. This attribute allows you to define a name for a method parameter, and when the creation of the method happens in T-SQL that name will be used instead of the .NET parameter name. This is useful when an organisation has specific code-standards for T-SQL and .NET and the standards for parameter names do not match. The attribute is located in a new dll, deployattributes.dll. This dll is installed in the GAC together with yukondeploy.dll and needs to be deployed to the database together with the assemblies that references the dll (the deployment tasks do that automatically).

January 10, 2006

Minor update to version 2.0 (no version change)

New features:

  • The assembly deployment task, DeployAsm, now deploys the assembly based on the binary representation of the assembly, not file location. This allows remote deployment.

Fixes:

  • Fixed an issue with altering an assembly using the UNCHECKED setting (an exception were thrown so the ALTER never happened).

December 27, 2005

Release 2.0 of yukondeploy.dll and first release of the DeployProperties GUI and the VS add-in and templates.

New features:

  • First release of a GUI front-end and VS add-in plus project and item templates.
  • Creation of DML test scripts
  • Ability to deploy to a non-default schema.

January 2005

First public release of the yukondeploy.dll assembly.