Asp.net C# database connection

Question

0.00/5 (No votes)

See more:

, +

newbie question..

What is the best way to configure the connection string, in Web.config or in a public method?

im trying to create web project connected to a database [MSSQL SERVER 2008 R2]..

What I have tried:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;

namespace asp
{
    public class connection
    {
        public string constring()
        {
            string str = @"SERVER=MACHUCA-PC\SQLEXPRESS;DATABASE=testdb;TRUSTED_CONNECTION=True";

            return str;
        }
    }
}

Posted 13-Oct-17 11:42am

akosisugar

Updated 13-Oct-17 20:57pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

OriginalGriff · Accepted Answer · 2017-10-13T20:23:00

Web.config

If you hard code the string you have to recompile the code when it changes.

And it changes every time you do maintenance, or upgrades. Because if it doesn't, your code tests against the production database and everything you do risks disaster. If you forget the WHERE clause for an UPDATE command for example: and all customers get their delivery address changed. Or you test a sale price reduction and everybody online gets the product for free perhaps. These things happen in development: and provided you are working against a development DB which is not the production one, it's no biggie. Testing against production is a very bad move!

If you hard code strings, you have to change your (tested, and perfect) code before release - and you can't test those changes except in production, where every mistake costs downtime and customers.