I am making a project using asp.net 4.0 and entity framework. I have implemented the routing feature introduced with asp.net 4.0.
There have been too many issues that I have faced with it.
Also there were issues with the use of AJAX.
Then there were the hyperlinks and image tags (had to use tilda everywhere etc).
But the most weired problem that I faced was and I am yet to resolve it is the issue of Page loading multiple times.
Can anyone tell me how to detect the reason for page loading multiple times and also sometimes few events go into infinite loop.
Also if anyone can help with resources to understand the routing feature thoroughly.
The routing feature is fantastic but I think it is still a bit immature. May be we may see improvements in the future versions of Asp.Net
I think routing is fairly stable and it certainly meets the most common needs.
Page loading multiple times is not a routing issue either, but it may seem to be that way. You need to look at the requests (use Fiddler, or even the Net tab in Firebug); things like empty image sources can call the default page because there's no target
URL, the domain is used, which in turn means the default document.
Infinite loops? I'd be very surprised if ASP.NET could generate that itself. Again it boils down to requests; what's being requested? Is it running through the routing engine? Is your route target calling something else?
I am unable to understand the automatic multiple page loads (same page loading multiple times) using firebug. Is there a dedicated tool to find just which request is causing the page load. I also read a few firebug tutorials specifically for the 'Net' tab,
but did not get any head way.
I haven't seen any explicit tutorials. I just use the net tab to view the requests, so it allows me to see if there's a request for the domain/page itself, rather than a resource (eg image file). Another tool i use if Fiddler (http://www.fiddler2.com/fiddler2/);
a free http proxy.
Another thing I supopse you could do is just to breakpoint on page load and examine Request.Url and Referrer, to see what's being requested and where from.