"Error Creating Control" on ASP.NET web form.

[owen]

Generally speaking, what does it mean when I see a "button" with red text
showing this message instead of the control I've dragged onto the web form
in Design View.? (But the page works fine at runtime). Does it indicate
a problem with References for example?

Thanks
Owen

PS. replies cc'd by email appreciated.
ow************@ mantix.com

[Herfried K. Wagner [MVP]]

Hello,

"owen" <sp**@spam.co m> schrieb:

Generally speaking, what does it mean when I see a
"button" with red text showing this message instead of
the control I've dragged onto the web form in Design
View.? (But the page works fine at runtime). Does
it indicate a problem with References for example?
You may want to turn to the ng for ASP.NET Web Controls questions:

news://msnews.microsoft.com/microsof...et.webcontrols

Web interface:

http://msdn.microsoft.com/newsgroups...et.webcontrols
PS. replies cc'd by email appreciated.

No.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
http://www.mvps.org/dotnet

[Cor]

Hi Owen,
First of all, if you next time have a message for this newsgroup, just ask
Error Creating Control on "VB.net" webform.

I don't know this message but I saw this on MSDN.

http://msdn.microsoft.com/library/de...bformspage.asp

\\\
If the Web Forms Designer cannot render a Web server control correctly, it
displays a grey box with the text "Error Creating Control." This often means
that the ASP.NET syntax of the control is incorrect - for example, if the
runat="server" attribute is missing in a Web server control element, you
will see this error. Point to the information icon (); a ToolTip is
displayed with details about the error.
///
Do you see that ToolTip and a grey box (you said a red text, but I don't
know if it is in a grey box)

Let me know if you did find the sollution or has some more information about
the error?.

Cor

[Peter Huang [MSFT]]

It seems not to be a valid email address, so I didn't send a notify email.

[owen]

"Cor" <no*@non.com> wrote in message
news:3f******** *************** @reader21.wxs.n l...

Hi Owen,
First of all, if you next time have a message for this newsgroup, just ask
Error Creating Control on "VB.net" webform.
Sorry but I thought I did that? Perhaps I misunderstood your point, but I
did put "VB.NET" in the subject of my post. (note: I'm sorry if the
crosspost was inappropriate but I thought it was relevant to all those
newsgroups).
Do you see that ToolTip and a grey box (you said a red text, but I don't
know if it is in a grey box)
Yes, there was a grey box with red text and an "i" icon which had a tooltip.
The tooltip said something about "object reference is not an instance of an
object".

Let me know if you did find the sollution or has some more information about the error?.

I found that it indicated a problem in the code underlying my control.
(which was a custom control based on a 3rd party Grid control). I
uninstalled and re-installed my 3rd party Grid control and this solved the
underlying problem in the code.... which removed the "Error Creating
Control" problem.

A search on Google newsgroups reveals that many people have been mystified
by "Error Creating Control".

It seems the main problem is the fact the error message is hidden inside a
tooltip, plus the fact it gives no indication of "where" the error occurrs.
It's so unhelpful, and the fact the project compiles perfectly just adds to
the mystery.

I now understand that certain things may work fine at Runtime but not at
Design time (for example if you use the Request object, which returns NULL
at design time). I would like to think MS will improve the way this is
handled in a future version of VS.NET so that it's clearer both what the
error is, and where it occurred. It would be better to show the error
itself instead of the insane "Error Creating Control", and perhaps make
clear when an error is a Design Time error *only*.

Owen

[owen]

"Peter Huang [MSFT]" <v-******@online.m icrosoft.com> wrote in message
news:mG******** ******@cpmsftng xa06.phx.gbl...

It seems not to be a valid email address, so I didn't send a notify email.

Hence the reason I put the valid email address in the post itself.

I never put my real email address in the message header, because it exposes
me to spambots who trawl newsgroups sending annoying unsolicited emails to
senders of all posts that include their real email address in the header.

Owen

[Cor]

Owen,

Sorry but I thought I did that? Perhaps I misunderstood your point, but I
did put "VB.NET" in the subject of my post. (note: I'm sorry if the
crosspost was inappropriate but I thought it was relevant to all those
newsgroups).
It is not important, but I changed ASP.NET in VB.NET in the reply see your
original post.
ASP.NET seems sometimes a red sign in this newsgroup for "this is not for
us".
The tooltip said something about "object reference is not an instance of an object".
That is of course important information
I found that it indicated a problem in the code underlying my control.
(which was a custom control based on a 3rd party Grid control). I
uninstalled and re-installed my 3rd party Grid control and this solved the
underlying problem in the code.... which removed the "Error Creating
Control" problem.
Cool
A search on Google newsgroups reveals that many people have been mystified
by "Error Creating Control".
I think webforms are in there childtime, yesterday I saw something strange
with code. It had to be done with HTML tags.
It would be better to show the error
itself instead of the insane "Error Creating Control", and perhaps make
clear when an error is a Design Time error *only*.

I do n't know if it helps for this, but an advice from someone active in
this newsgroup is set "Option Strict On" in the top of your code form.
And sometimes that helps you to find the error at design time (but your
problem is oposite I know).

But I am glad the problem is solved and that is the main thing.

Cor