If you use a Using declaration on your connection, .NET automatically closes it when it reaches the end Using call.
In VB
Code:
Dim conn as new Connection....
Using Conn
End Using
C#
Code:
connection conn = new Connection...
using (conn)
{
}
I still tend to include calls to Close() methods and have using as a fail safe to catch any I miss. Bit of overkill maybe...
In terms of efficiency, if you think about it in terms of getting the information you want in the least number of hops. So, a call to a database will always be less efficient as it's another hop to getting the data you need.
It's more a case of ascertaining what functionality you need. If it's a simple yes/no dropdown, then hard code it. If it's likely to change / update regularly then use a database.
If using a database, it may be more efficient is to pass the values into cache on Application Start and then access them from there each time you need them. Then if they get updated, make sure you call a method to update the cached version.
All depends how often the values will be needed, how much memory would they take up etc. It's a matter of measuring how much resource would be used against the increased efficiency of getting the data from memory rather than the db each time.
Hope that helps.
ASP Free Forums Sponsor:
October 30th, 2009, 10:20 AM
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
