VS.NET 2003 Bug when ASP.NET control is in Design mode

[~~~ .NET Ed ~~~]

Odd problem it is... on the design surface the web control is shown with red
letters claiming that VS.NET was "Unable to create Control". But the entire
assembly compiles flawlessly and even the test page displays the "damaged"
controls perfectly. Looks like a VS.NET bug.

 

[John Saunders]

Odd problem it is... on the design surface the web control is shown with
red
letters claiming that VS.NET was "Unable to create Control". But the
entire
assembly compiles flawlessly and even the test page displays the "damaged"
controls perfectly. Looks like a VS.NET bug.

Bug: sometimes VS.NET fails to create the control for no good reason.

Not likely!

What's more likely is that there _is_ a good reason, but VS.NET isn't nice
enough to tell you what that reason is.

At times like these, it's necessary to debug the design-time behavior of the
control. To do this, I usually just start up another instance of Visual
Studio.NET, then use Tools->Debug Processes to select the original instance
of devenv.exe. I then use the Debug->Exceptions dialog have the likely
culprits break into the debugger immediately. I then just go over to the
original and reproduce the problem. Chances are, you'll catch an exception
in the debugger (the favorite being NullReferenceException).

John Saunders

 

[Saravanan K V]

Hi,

You have not told what control you are using. Some times, if you have a
control which has only run time license, you may see this issue.