Class Library Set Property / Field Default or Initial Values?
Q. How do I set the Property / Field Default or Initial values in a Class Library (.dll)?
I've read about Attributes and it doesn't seem the best approach. The example below is a simple illustration of properties/fields which need to be used, but don't neccessarilly need user setup. Note: it'a a static class.
I've read about Attributes and it doesn't seem the best approach. The example below is a simple illustration of properties/fields which need to be used, but don't neccessarilly need user setup. Note: it'a a static class.
public static class FtpClient
{
private static bool _useBinary = false;
public static bool UseBinary
{
set { _useBinary = value; }
}
}
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
That would work (should work for a non-static class [and members] as well). Standard OO practices typically have you initialize a class within its constructor. .NET has something called "object initialization", which can substitute for a equivalent constructor or the approach above. Object initialization does not work with static code, however. Object initialization looks like this:
The braces and the assignment of "Hello World!" to the Message property denote object initialization. Any non-static property can be initialized in this fashion.
I'm not sure how Attributes would help you here. There is a DefaultValueAttribute class, but it is more for code generators than for actual runtime code. This attribute will not set a default value for your objects at runtime.
class Foo
{
public string Message { get; set; }
}
class Program
{
static void Main()
{
Foo f = new Foo()
{
Message = "Hello World!";
};
}
}
The braces and the assignment of "Hello World!" to the Message property denote object initialization. Any non-static property can be initialized in this fashion.
I'm not sure how Attributes would help you here. There is a DefaultValueAttribute class, but it is more for code generators than for actual runtime code. This attribute will not set a default value for your objects at runtime.
Well as I mentioned, what you have shown is a viable approach. You could also define a static constructor (if you so desired), but its net effect would be the same as what you are currently doing.
e.g.
Note: A static constructor isn't called directly. It will be invoked automatically the moment you refer to any of the class' static members or the first time you create an instance of class (if that class is non-static). The initialization you have shown above is also executed in this manner.
e.g.
...
static FtpClient()
{
_useBinary = false;
}
...
Note: A static constructor isn't called directly. It will be invoked automatically the moment you refer to any of the class' static members or the first time you create an instance of class (if that class is non-static). The initialization you have shown above is also executed in this manner.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial