I required to get details about ConfigurationManager in ASP.NET

Question

5.00/5 (1 vote)

See more:

What is the difference between

C#

public SqlConnection getConnection()
   {SqlConnection conn;
       string str = ConfigurationManager.ConnectionStrings["MyConnection"].ConnectionString;
       conn = new SqlConnection(str);
       conn.Open();
       return conn;
   }

C#

public SqlConnection getConnection()
    {
        string str = "Data source=Gisserver;initial catalog=Database;Uid=sa;pwd=sa";
        conn = new SqlConnection(str);
        conn.Open();
        return conn;
    }

I use second one then connection established . Why not executed first properly.

Posted 5-May-10 18:34pm

vipin.sethumadhavan

Add a Solution

4 solutions

Solution 4

The main advantage of it is portability and decoupled design.

Let's check the other side, if we hard code the connection string then what is disadvantage of it.

1. First and foremost it is hard-coded. So if I want to reuse, it is not possible. I must hard code again and again whenever I want to reuse the same connection string.

2. The second and most important disadvantage of it is once we build the project and we need to change the connection string (either database server name change or database name change) then we need to change everywhere wherever we hard coded our connection string.
[While in ~~second~~ first case we need to change only at one place (in config file) and it will take new connection string]

Hope you understand!
----
Edit (by Ankur): In the last line you must be talking about the first case. :)

Posted 5-May-10 23:22pm

Peace ON

Updated 6-May-10 1:03am

v2

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ankur^\m/ · Accepted Answer · 2010-05-05T20:13:00

The difference between the 1st and 2nd code snippet is:

In the first case, you are storing the connection string in a config file.
The advantage being, it is not hard coded in your application and so it can be easily configured. What I mean is you may have a situation where you need to change your connection string, with this option you can easily change the server name, database, or authentication information without editing individual Web pages. Additionally, you can secure the connection string using encryption
In second case, you are hard coding the connection string which is not a good practice for the reason I explained above.

The other responders have already told you why the first case is not working. :)

Viral Upadhyay · Accepted Answer · 2010-05-05T18:43:00

Solution 1

I don't think there is a problem in your code for first one you should check if you add connection string properly in you web config file.
This is the only one problem i think in it.

Posted 5-May-10 18:43pm

Viral Upadhyay

dineshmehra1 · Accepted Answer · 2010-05-05T19:49:00

in case of the first one i.e
ConfigurationManager.ConnectionStrings["MyConnection"].ConnectionString
u have to put your connection string in web.config like

XML

<appSettings>
  <add key="MyConnection" value="Data Source=RITESH\SQLEXPRESS;Initial Catalog=Test1; Integrated Security=true"/>
</appSettings>

and its secure way to keep connection string in web config.
there should not be any issue og not getting connection this way.

==================================================================
Arun : I don't think that this is correct.What you specified is ConfigurationManager.AppSettings["MyConnection"] not ConfigurationManager.ConnectionStrings["MyConnection"].
==================================================================

I required to get details about ConfigurationManager in ASP.NET

4 solutions

Solution 3

Solution 1

Solution 2

Solution 4

Add your solution here

Preview 0

I required to get details about ConfigurationManager in ASP.NET

4 solutions

Solution 3

Solution 1

Solution 2

Solution 4

Add your solution here

Preview 0

Existing Members

...or Join us