Suggestion: Go to an MS Access forum.
sql
Every time I move my project from my computer to the testing server I have to change the connection string references in the aspx side and in my code behind.
For the code behind I declared the SqlConnection string at the top of the code-behind page for both connection strings and comment out the one not in use. Obviously I then comment out the string not in use in the WebConfig as well.
Being superlatively lazy I always look for the easiest and quickest way to do most anything - connection strings included. Having to comment out strings twice brought rise to the question of whether I can refer to the connection string in the web.config file from the code-behind page. I'm sure it can be done, and I did a good amount of hunting around, but I couldn't find any examples of code that would do that.
Currently, as I said above, I have two connection strings declared at the top of my code-behind. Here's an example of one:
Private sqlConnAs New SqlConnection("Data Source=DATABASESERVER;Initial Catalog=DATABASE;User ID=USER;Password=PASSWORD")Then, I just use sqlConn as usual in my binding without having to "dim" it in every sub:
sdaPersonnel =New SqlDataAdapter(strSqlPersonnel, sqlConn)
Then there's the SqlConnections set up by the wizard on the aspx side:
<asp:SqlDataSource ID="sqlDataSourcePayrollCompany" Runat="Server" ConnectionString="<%$ ConnectionStrings:DATABASECONNECTIONSTRING%>" ...>
And for the connection in the web.config:
<add name="DATABASECONNECTIONSTRING" connectionString="Data Source=DATABASESERVER;Initial Catalog=DATABASE;User ID=USER;Password=PASSWORD" providerName="System.Data.SqlClient" />
So, what would be the code in the code-behind page to refer to the connection string in the web.config file?
Thanks!
To refer to the connection string via code: ConfigurationManager.ConnectionStrings["<ConnectionStringName>"]|||Hey, Stiletto, Thanks! That did the trick (or, at least, it got me on the right track). I wasn't exaclty sure how to actually add that to my connection string code, so I had to do some hunting and trying different syntax, but ended up with this working:
Private sqlConnAs New SqlConnection(ConfigurationManager.ConnectionStrings("DATABASECONNECTIONSTRING").ConnectionString) Thanks again!
I created a SQL Server Project in VS 2005, and tried to add a reference to SQLDMO Object dll. But the reference --> add reference, does not allow it. It does not work, even if I set the Assembly Permission Level to UNAFE/EXTERNAL ACCESS.
Reason I'm trying to do this:
We have a SQL 2000 stored procedure that uses SQLDMO using sp_OACreate to BCP files to database. We are converting to 2005 and because of SOX restrictions, I'm trying to replace the sp_OACreate part with external stored procedure written in C#.
According to BOL, I thought atleast UNSAFE should support this, but it seems not.
Probably, I'm expecting too much..
Your help is greatly appreciated.
Thanks
Thanks to Vineet Rao's posting to one of of the answers on this forum, to a similar problem.
I registered "signed" InterOp.SQLDMO.dll (which is obtained by referecing to a regular project) , as UNSAFE, and it appeared in the Reference section of SQL Server Project.
Thanks
Baskar
Hi,
I'm using Visual Studio Beta 1 with SQL Server 2005 Beta 2 and have created a SQL Server Project.
The first thing I tried was to add a reference to a C# class library project that contains many C# tools I like.
Bad news, I get the following error message:
"A reference to 'csharplibrary' could not be added. SQL Server projects can reference only other SQL Server projects."
My question is: is this behavior a limitation of any of the Betas, or is it going to stay? This greatly limits the use of the CLR in SQL Server, IMO.
Martin
Hi,There are various different approaches you can follow to get your scenario working.
1. You can pre-register all the assemblies that you want to refer in your project - inside your SQL Server database using the CREATE ASSEMBLY statement. Once you are done with that, you can refer them in Visual Studio SQL Server projects using the add reference (they should be shown in the list).
2. You can use class library projects (that allows you to reference any assemblies on the disk) to build your assembly and then register them via SQL Server Management Studio using the CREATE ASSEMBLY statement.
The behavior that you are seeing is going to stay as-is in Visual Studio 2005.
Thanks,
-Vineet.|||
Vineet, thanks for that precious information. It's working... almost.
The assembly is registered, but I get the following error when trying to reference it in Visual Studio for the SQL Server project:
A reference to 'classlibrary' could not be added. This is not a valid assembly or COM component. Only assemblies with extension 'dll' or 'manifest' or COM components can be referenced. Please make sure that the file is accessible, and that it is a valid assembly or COM component.
I've used the same assembly in other VS projects and it's working fine. It's a very basic C# class library/dll with one class containing one static method (no static field).
Any suggestions?
Martin|||
Hi Martin,
This is a known bug and has been fixed in Visual Studio 2005 feb CTP onwards.
Thanks,
-Vineet.
ie, instead of ...
red
blue
red
green
it would return ...
red
blue
green
Sorry for the trouble and thanks.DISTINCT or GROUP BY will do that for you.
Example:
SELECT DISTINCT colour
FROM ColourTable
--
David Portas
----
Please reply only to the newsgroup
--|||Thanks, David!
On Thu, 1 Jan 2004 23:47:08 -0000, "David Portas"
<REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote:
>DISTINCT or GROUP BY will do that for you.
>Example:
>SELECT DISTINCT colour
> FROM ColourTable
>--
>David Portas
>----
>Please reply only to the newsgroup