CODEWITHSUNDEEP
c#composite-controls
Sankar
Sankar

Reputation:

Error Creating Control - Custom Control

I have a custom control and it works fine...except that the control cannot be rendered on Design Time. ( I am using VS 2008)

I am thinking many people who develop custom controls encounter this problem...The error I get is "Error Creating Control - CustomControlName" Object reference not set to an instance of an object.

I want a work around. or at least debug this...(Since this is a design time issue how to debug?)

I have tried if( !DesignMode) code on OnInit, OnPreRender, RenderContents, CreateChildControls Methods ( I am just shooting in the dark)...

Help pls. I really hope this is not a VS bug!

Upvotes: 3

Views: 2820

Answers (4)

shadi
shadi

Reputation:

Glenn, the error ur getting a VS bug and no fix has been released yet.

Upvotes: 0

Glenn Slaven
Glenn Slaven

Reputation: 34183

In your OnPreRender & CreateChildControls methods it's making a call to this.Page. You might want to try wrapping them in a

if (this.Page != null)
{
.....
}

Because I don't think you'll have a Page object at that point & I'm pretty sure PreRender & CreateChildControls will be called in design view. I haven't written custom server controls for a while though, so I could be wrong (been working in MVC lately).

Upvotes: 0

KMessenger
KMessenger

Reputation: 81

As Glenn mentioned the first issue could be no parameterless constructor.

The second could be you are calling methods during the OnLoad or other methods you mentioned that have parameters that are not initialized or some sort of attempt at database calls etc that is normally done at run-time.

Unless they fixed this bug recently* and I'm not aware, something to keep in mind is the DesignMode property works for the first and second level of nested controls but beyond that it normally doesn't work right. (Such as form containing a UserControl[1] that holds another UserControl[2], the DesignMode works on the form and [1] but not [2]).

Also to agree with Glenn, seeing some of the code will help.

*From my very recent experience working with nested usercontrols it hasn't been fixed.

Upvotes: 0

Glenn Slaven
Glenn Slaven

Reputation: 34183

BFree's comment is the most likely issue, for a control to display in the design view it needs a parameterless constructor as the design viewer doesn't know how you would normally instantiate the control.

If you do have a parameterless constructor, can you paste some code in to show what's happening?

Upvotes: 1

Related Questions