nm, i just found it!
may I add actual properties to the COnfiguration class for minimizing having to "know" what the properties all are?
in theory, having that loose coupling is nice, but we can also deprecate properties via Obsolete()...
Code:
public class Configuration
#if NET_2_0
/// <summary>
/// Gets or sets the Name of the Connection String from .NET Configuration <connectionStrings> section.
/// </summary>
/// <remarks>New to .NET 2.0, the configuration has a
/// <connectionStrings> section. Refer to the documentation for the <connectionStrings> section.
public string ConnectionStringName
{
get { return (string)this.Properties[Environment.ConnectionStringName]; }
set { this.Properties[Environment.ConnectionStringName]=value; }
}
#endif
... and so forth
Login
FAQ
Search
