User Control access fails in debug mode, works in release mode

[rbg.net]

I have a custom usercontrol in ASP.NET 1.1 named BreadCrumb.ascx which
contains another control also called BreadCrumb.ascx within itself.

Thus the parent BreadCrumb.ascx control is simply a container of the
real (child) Breadcrumb.ascx control.

When I use this parent BreadCrumb.ascx user control within a page. I
can successfully access the page if the debug attribute for the
compilation element in web.config is set to false.

However when the debug attribute is set to true. The page access fails
with the error on this line in the
WINNT\.NETFramework\v1.1.4322\0jhhfgf.cs file :

object __ctrl = ASP.Breadcrumb_ascx
this.breadcrumb = __ctrl

It says cannot map this.breadcrumb to ASP.Breadcrumb_ascx
NOTE THAT THE ABOVE IS THE COMPILER GENERATED .CS FILE

Where ASP.Breadcrumb_ascx is the parent BreadCrumb (container) control
and this.breadcrumb refers to the child Breadcrumb control.

The error is correct in itself, however the point that I dont
understand is why the code works perfectly fine when debug = false, but
fails when debug = true in web.config. Obviously in the debug = false
case the COMPILER GENERATED .CS file isn't accessed.

What I need to understand is why such error happens when debug = true.
Essentially why does the compiler generate a CODE which maps
this.breadcrumb TO ASP.BREADCRUMB_ASCX.

TIA

 

[Peter Zolja]

What I need to understand is why such error happens when debug = true.

Essentially why does the compiler generate a CODE which maps
this.breadcrumb TO ASP.BREADCRUMB_ASCX.

Have you tried debugging your code with VS debugging? I'm not sure how easy
it is with VS2003, but in VS2005 is fairly easy to debug.