Let me say this and I want to make it clear that I am not changing the original subject of my question. You'll see later that I'm maintaining my original question here. I'm just making my question richer so you can help finding out why ASP.Net performance degrades sometimes

Naughton's answer in a recent post comes like this:

greatbear

protected void Page_Init(object sender, EventArgs e)
        {
            table = DynamicDataRouteHandler.GetRequestMetaTable(Context);
            GridView1.SetMetaTable(table, table.GetColumnValuesFromRoute(Context));
            GridDataSource.EntityTypeFilter = table.EntityType.Name;
            if(table.Name.Equals("Employee")
                GridDataSource.Where = "it.DEPT>3000";
        }

If you see here in the code below,

table = DynamicDataRouteHandler.GetRequestMetaTable(Context);

"table" is a variable of the type DynamicDataRouteHandler.GetRequestMetaTable(Context) NOT A STRING

But Dynamic Data maintains its properties just when it is executing that piece of code. After that "table" IT'SGONE

There is no way of recreating that sentence but in that very method

I'm saying this in order to show you something I was telling you before: programmers need help with customization and the lack of documentation makes you write messy code which might as well be avoided if proper training were published on Dynamic Data

Coming to our point:  don't know if that pieces of code might be interfering with ASP.Net performance

BUT THERE IS NO WAY OF CHECKING THIS OUT BY MEANS OF WHAT YOU SAID: DEBUGGING

Maybe with any other tool but Dynamic Data. No way to do that Jose!

Thanks