Click here to Skip to main content
16,018,006 members
Articles / Programming Languages / C#
Article

Setting Default Values on Automatic Properties

Rate me:
Please Sign up or sign in to vote.
3.53/5 (8 votes)
14 May 2008CPOL2 min read 97.9K   197   23   36
An article on implementing default values on Automatic Properties

Introduction

C# 3.0 introduces a great new feature called Automatic Properties, and if you haven’t already read about them, I would encourage you to read Scott Guthrie's introductory post.

As great as they are and as much time as they save, Automatic Properties have a serious drawback – you can’t set the default value of the property. Instead, the compiler will initialize value properties to 0, reference properties to null, and enum’s to the first member, and while this might work for some applications, it wasn’t working for mine.

Background

When I thought about the implementation, two options became apparent. One, I could create a base object class and have all of my classes inherit from this base class. This however isn’t a great solution because a number of my classes inherit from other classes outside of my control, and since .NET does not support multiple inheritances, it was clear this wasn’t going to work. To my rescue was the also new C# 3.0 feature, Extension Methods. If you haven’t already heard about Extension Methods, I’d recommend reading another one of Scott Guthrie's blog posts about them.

Using the Code

Using the code requires that you decorate your properties with an attribute already available in the System.ComponentModel namespace – if you haven’t already guessed it, it’s the aptly named DefaultValueAttribute attribute. As well, it requires a quick call to the InitDefaults() extension method from the constructor which I will discuss a bit later.

The attached code supplies a demo implementation of the TestObject and TestObjectInherited classes:

C#
public class TestObject
    {
        public TestObject()
        {
            this.InitDefaults();
        }

        [DefaultValue(-45)]
        public int DefaultInt
        {
            get;
            set;
        }

        [DefaultValue(10.23)]
        public double DefaultDouble
        {
            get;
            set;
        }

        [DefaultValue(true)]
        public bool DefaultBool
        {
            get;
            set;
        }

        [DefaultValue(TestEnum.Value2)]
        public TestEnum DefaultEnum
        {
            get;
            set;
        }

        [DefaultValue("DefaultString!")]
        public string DefaultString
        {
            get;
            set;
        }

        public string StringWithoutDefault
        {
            get;
            set;
        }

        public string ValueOfPrivateProperty
        {
            get
            {
                return PrivateProperty;
            }
        }

        [DefaultValue("This is a private property!")]
        protected string PrivateProperty
        {
            get;
            set;        
        }
    }

The magical InitDefaults() method is implemented as an extension method which uses reflection to set the value of the properties to the default value:

C#
public static void InitDefaults(this object o)
        {
            PropertyInfo[] props = o.GetType().GetProperties(BindingFlags.Public | 
                BindingFlags.NonPublic | BindingFlags.Instance | BindingFlags.Static);

            for (int i = 0; i < props.Length; i++)
            {
                PropertyInfo prop = props[i];                

                if (prop.GetCustomAttributes(true).Length > 0)
                {
                    object[] defaultValueAttribute = 
                        prop.GetCustomAttributes(typeof(DefaultValueAttribute), true);

                    if (defaultValueAttribute != null)                    
                    {
                        DefaultValueAttribute dva = 
                            defaultValueAttribute[0] as DefaultValueAttribute;
                        
                        if(dva != null)
                            prop.SetValue(o, dva.Value, null);                                
                    }
                }
            }
        }

Points of Interest

I decided to support initializing the default value of properties in inherited classes, but if you don’t want this behavior, you can simply pass false to GetCustomAttributes().

C#
if (prop.GetCustomAttributes(false).Length > 0)
                {
                    object[] defaultValueAttribute = prop.GetCustomAttributes
                        (typeof(DefaultValueAttribute), false);

                    if (defaultValueAttribute != null)                    
                    {
                        DefaultValueAttribute dva = 
                            defaultValueAttribute[0] as DefaultValueAttribute;
                        
                        if(dva != null)
                            prop.SetValue(o, dva.Value, null);                                
                    }
                }

History

  • 14th May, 2008: Initial post

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Web Developer
Canada Canada
Steven is VP Development at MBC Computer Solutions Ltd. (http://www.mbccs.com), a Richmond Hill based company specializing in e-Business Application Development, e-Store Solutions, Managed Co-Location and Proactive IT services.

Steven has over 10 years experience in software and hardware design and is experienced with a large array of platforms, technologies and languages.

In his spare time, Steven enjoys a wide array of music, is an avid skier and enjoys spending time with friends.

Steven is the primary contributor of MBC's blog which can be read at http://blogs.mbccs.com/mbccomputersolutions

Comments and Discussions

 
GeneralRe: I Don't See The Value In Automatic Properties Pin
Steven Berkovitz15-May-08 9:44
Steven Berkovitz15-May-08 9:44 
GeneralRe: I Don't See The Value In Automatic Properties Pin
William E. Kempf15-May-08 9:46
William E. Kempf15-May-08 9:46 
GeneralRe: I Don't See The Value In Automatic Properties Pin
PIEBALDconsult15-May-08 9:49
mvePIEBALDconsult15-May-08 9:49 
GeneralRe: I Don't See The Value In Automatic Properties Pin
Steven Berkovitz15-May-08 9:50
Steven Berkovitz15-May-08 9:50 
GeneralRe: I Don't See The Value In Automatic Properties Pin
PIEBALDconsult15-May-08 10:11
mvePIEBALDconsult15-May-08 10:11 
GeneralRe: I Don't See The Value In Automatic Properties Pin
William E. Kempf15-May-08 10:44
William E. Kempf15-May-08 10:44 
GeneralRe: I Don't See The Value In Automatic Properties Pin
PIEBALDconsult15-May-08 12:03
mvePIEBALDconsult15-May-08 12:03 
GeneralRe: I Don't See The Value In Automatic Properties Pin
William E. Kempf16-May-08 2:47
William E. Kempf16-May-08 2:47 
PIEBALDconsult wrote:
New here? I'll assume you mean a System.Collections.Generic.List<t>, but how can I know if you don't tell me? I use them all the time, but I fully qualify them to be sure that no one reading the code is confused that I may or may not be using some WidgetCo.List<t> of which they're unaware.


You qualify every name? I'm glad I don't have to work on any of the code bases you do. That's just insane. (If you take offense at that, think about how I should have taken the "new here?" crack.)

The argument still falls apart. Just as you can qualify a type with the full namespace, I can qualify an extension method with the full name.

Some.Stupid.Namespace.SomeExtensions.SomeExtensionMethod(theInstance);


I really don't get what your argument is.

PIEBALDconsult wrote:
Many posters here will post a snippet of code and say "this Gizmo isn't working", and I have no idea what that gizmo is, what namespace it's in, and where I can get information on it, because they don't fully qualify it and don't include the appropriate using directive; in many cases the poster probably doesn't even know the namespace.


In this specific case, it didn't matter what the namespace was, so why should I have included it? And given the "new here" crack, I'm assuming your also baiting me with the last sentence. Sorry, I won't rise to it.

PIEBALDconsult wrote:
Case in point.


About namespaces? Would it have helped you if I told you it was MyReallyCoolNamespace.ComponentModel.ObjectContainer? Come on buddy, this wasn't a reference to any BCL components, and you have to be smart enough to know that.

At this point, I think you're just being argumentative. I see no point in continuing the discussion.

William E. Kempf

GeneralRe: I Don't See The Value In Automatic Properties Pin
PIEBALDconsult16-May-08 10:42
mvePIEBALDconsult16-May-08 10:42 
GeneralRe: I Don't See The Value In Automatic Properties Pin
William E. Kempf16-May-08 14:59
William E. Kempf16-May-08 14:59 
GeneralRe: I Don't See The Value In Automatic Properties Pin
PIEBALDconsult16-May-08 19:30
mvePIEBALDconsult16-May-08 19:30 
GeneralRe: I Don't See The Value In Automatic Properties Pin
PIEBALDconsult15-May-08 14:22
mvePIEBALDconsult15-May-08 14:22 
GeneralRe: I Don't See The Value In Automatic Properties Pin
William E. Kempf16-May-08 2:49
William E. Kempf16-May-08 2:49 
GeneralRe: I Don't See The Value In Automatic Properties Pin
Polymorpher21-May-08 12:39
Polymorpher21-May-08 12:39 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.