easiest way to upload a C# class library to a SQL server 2005 and deploy as CLR function

[DR]

easiest way to upload a C# class library to a SQL server 2005 and deploy as
CLR function

Do I have to upload the .dll and then run sql command to load it into sql
server, or is there a more integrated way to do this in visual studio 2005
with a SQL Server Project? or do i have to manualu upload the DLL in all
cases? Any tutorial on CLR with Visual Studio 2005 IDE to Sql Server 2005?

[Alberto Poblacion]

"DR" <so*******************@yahoo.comwrote in message
news:OD**************@TK2MSFTNGP04.phx.gbl...

easiest way to upload a C# class library to a SQL server 2005 and deploy
as CLR function

Do I have to upload the .dll and then run sql command to load it into sql
server, or is there a more integrated way to do this in visual studio 2005
with a SQL Server Project? or do i have to manualu upload the DLL in all
cases?

If you decorate your source code with the adequate attributes, such as
[Microsoft.SqlServer.Server.SqlFunction(Name:="what ever")], then Visual
Studio is able to deploy it automatically to SqlServer when you run the test
project. No need to manually upload the dll during development time. You may
still want to write a sql script with all the CREATE statements, to be used
when you need to deploy or redeploy your dll on the production servers.

[DR]

thanks!

"Alberto Poblacion" <ea******************************@poblacion.orgwro te
in message news:u6**************@TK2MSFTNGP02.phx.gbl...

"DR" <so*******************@yahoo.comwrote in message
news:OD**************@TK2MSFTNGP04.phx.gbl...

>easiest way to upload a C# class library to a SQL server 2005 and deploy
as CLR function

Do I have to upload the .dll and then run sql command to load it into sql
server, or is there a more integrated way to do this in visual studio
2005 with a SQL Server Project? or do i have to manualu upload the DLL in
all cases?

If you decorate your source code with the adequate attributes, such as
[Microsoft.SqlServer.Server.SqlFunction(Name:="what ever")], then Visual
Studio is able to deploy it automatically to SqlServer when you run the
test project. No need to manually upload the dll during development time.
You may still want to write a sql script with all the CREATE statements,
to be used when you need to deploy or redeploy your dll on the production
servers.