in layered settlement removed dataaccess covering .net where should tie twine managed?

there enlarged controlling dress here where i work tie twine lives web.config, sql tie vigilant instantiated controlling retard tie twine upheld dataobjects constructor (via createinstance slight constructor private). something this:

using(sqlconnection conn = new sqlconnection(configurationmanager.connectionstrings["connectionstring"].connectionstring))
{
    dataobject foo = dataobject.createinstance(conn);
    foo.someproperty = "some value";
    foo.insert();
}

this smells me.. i don't know. shouldn't datalayer category library grateful tie objects tie strings? i'd beholden know others doing any good online articles kind settlement decisions.

consider projects work always sql server backends severely puzzled change. bureau provider settlement i'm after. it's some-more where accountability lies where config settings should managed information covering operation.