Passing connection string to DLL

[Jeff]

I have a main project which references several DLLs. Each DLL will
access the same database as the main project. I'm storing the
connection string within the main project's "web.config " file, so in
theory the DLLs do not have "visibility " to the connection string.

I considered creating a public sub within each DLL (class) which allows
the connection string to be set (but not read):

Public Class myClass
'DATA CONNECTION
Private mobjDataConnect ion As New SqlClient.SqlCo nnection

Public Sub SetConnectionSt ring(ByVal strValue As String)
mobjDataConnect ion.ConnectionS tring = strValue
End Sub

...
...
End Class

This way, only the main project's Web.Config file needs to contain the
connection string. The main project will simply pass the string to the
"SetConnectionS tring" method of the class.

Is this secure? If not, any suggestions?

[Steve C. Orr [MVP, MCSD]]

Yes, this sounds like a good solution to me.
Another solution would be to have the middle tier (your business logic DLLs)
manage the connection string so the UI layer (your pages) wouldn't have any
visibility to it.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"Jeff" <jr***@usa.ne t> wrote in message
news:11******** **************@ l41g2000cwc.goo glegroups.com.. .

I have a main project which references several DLLs. Each DLL will
access the same database as the main project. I'm storing the
connection string within the main project's "web.config " file, so in
theory the DLLs do not have "visibility " to the connection string.

I considered creating a public sub within each DLL (class) which allows
the connection string to be set (but not read):

Public Class myClass
'DATA CONNECTION
Private mobjDataConnect ion As New SqlClient.SqlCo nnection

Public Sub SetConnectionSt ring(ByVal strValue As String)
mobjDataConnect ion.ConnectionS tring = strValue
End Sub

...
...
End Class

This way, only the main project's Web.Config file needs to contain the
connection string. The main project will simply pass the string to the
"SetConnectionS tring" method of the class.

Is this secure? If not, any suggestions?

[Jeff]

"Another solution would be to have the middle tier (your business logic
DLLs)
manage the connection string so the UI layer (your pages) wouldn't have
any
visibility to it."

Thanks for the reply. Regarding your other recommended approach, how
would these DLLs have their own visibility to the main project's
"web.config " file? IOW, how would they know the connection string?
Would I have to give each project (DLL) its own web.config file?

I should clarify that each "business logic DLL" is being
developed/compiled within its own project which does *not* have a
"web.config " file.

[Steve C. Orr [MVP, MCSD]]

In this case the web.config might not be as easy, but any old XML file could
work just as well. You could make it as simple or complex as you need.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"Jeff" <jr***@usa.ne t> wrote in message
news:11******** **************@ g14g2000cwa.goo glegroups.com.. .

"Another solution would be to have the middle tier (your business logic
DLLs)
manage the connection string so the UI layer (your pages) wouldn't have
any
visibility to it."

Thanks for the reply. Regarding your other recommended approach, how
would these DLLs have their own visibility to the main project's
"web.config " file? IOW, how would they know the connection string?
Would I have to give each project (DLL) its own web.config file?

I should clarify that each "business logic DLL" is being
developed/compiled within its own project which does *not* have a
"web.config " file.

[Mythran]

"Steve C. Orr [MVP, MCSD]" <St***@Orr.ne t> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

In this case the web.config might not be as easy, but any old XML file
could work just as well. You could make it as simple or complex as you
need.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"Jeff" <jr***@usa.ne t> wrote in message
news:11******** **************@ g14g2000cwa.goo glegroups.com.. .

"Another solution would be to have the middle tier (your business logic
DLLs)
manage the connection string so the UI layer (your pages) wouldn't have
any
visibility to it."

Thanks for the reply. Regarding your other recommended approach, how
would these DLLs have their own visibility to the main project's
"web.config " file? IOW, how would they know the connection string?
Would I have to give each project (DLL) its own web.config file?

I should clarify that each "business logic DLL" is being
developed/compiled within its own project which does *not* have a
"web.config " file.

You know, in your dll, you don't need to have SetConnectionSt ring to get the
connection string that is stored in the <appSettings> section of the
web.config file?

All you need is to call
Configuration.C onfigurationSet tings.AppSettin gs.GetConfig("C onnectionString ")
to grab the key/value pair with the key ConnectionStrin g. You can call this
from the DAL directly. This way, if you have a Windows Forms application
that needs to use the same BLL/DAL objects that the Web UI uses, it will
define the ConnectionStrin g in it's app.config file and the DAL won't need
to be changed at all. Just calling the GetConfig will do the trick...

Not sure if you knew that or not :)

Mythran