How to have code in the constructor that will NOT be executed at design time by Visual Studio?

Question

I have a method call in the constructor of my user control that does something that won\'t work at design time (connecting to a database), and Visual Studio just bailed out

Answer 1

Have a look at this

Component.DesignMode Property

Answer 2

public SomeViewModel()
{
    if (!IsInDesignMode)
    {
        DoWork();
    }
}

This code above if you are working on the actual UI that you are trying to work on. In a situation that you have something like this on a control, when you switch back to the designer for that control it's ok and no design time error. Now if you added that control that contains the code above to some other Form or another control via dragging it from the toolbox, it will show some design time errors.

Answer 3

In Windows Forms?

if (!DesignMode)
{
    // code that shouldn't be executed at design time
}

As others have mentioned, this won't work in the constructor. It's often used in the Form.Load event.

Answer 4

I liked Michael Petrotta's approach for Windows Forms. If anyone wants to apply the same technique to WPF, simply use IsInDesignMode.

Example:

public SomeViewModel()
{
    if (!IsInDesignMode)
    {
        DoWork();
    }
}

Answer 5

As others have stated, you can use the DesignMode property of the Component class. However, you will not be able to do this in the constructor of your control. The DesignMode property is always false in the constructor and methods called by the constructor. To get around this, re-factor your code to connect to the database in the OnLoad() callback. The DesignMode property is valid at that point. See here for the reasoning (look for the DesignMode section of the article).

I just ran across this blog entry that describes how to use the System.ComponentModel.LicenseManager.UsageMode property for doing the same thing. The blog describes an additional shortcoming of the DesignMode property when dealing with nested controls. Apparently, the UsageMode property doesn't have the same shortcomings and is available for use in the constructor. I cannot personally vouch for it, but might be worthwhile looking into.