I created a Sql Server project so I could play with writing CLR functions. During the project set-up I was required to choose a data source that is then stored in the project. All fine and good. Functions written, deployed, and working.

Now I want to change the "hard-wired" connection so I can deploy my functions to another database on the same server. I have gone to the properties tab on the project and it won't let me change the connection string. The problem is when I select the server instance and the new database target it cannot connect. Odd thing is I can see the new database I want in the server explorer in the IDE. I tried changing it in the xxx.csproj.user file of the project ( the XML ) and it basically ignored it and kept using the old connection string. I have looked in every file in the project and cannot find any other place I reference the connect string. Where else might it be stored?

Both the old and new database exist on the server and I have full permissions. The server instance ( local on my machine ) also allows remote connections and has the CLR option turned on.

Any ideas and while I am at it how do I allow the connection string to be changed at runtime and still be allowed to use the context connection attribute?

Thanks,

MW

Does the Deploy Solution option on the Build menu help?

http://msdn.microsoft.com/en-us/library/dahcx0ww(VS.80).aspx

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.

I was using that and there appear to be no options.

I figure what I will have to do is create my sprocs/UDF's as a C# class library and always go and get the connection string when I need it rather than use the context connection attribute in a Sql Server project. Then I can compile the code and deploy it manually by using the CREATE ASSEMBLY command on the server.

Bummer.