Infinities Loop

This question comes up from time to time, to time. If you understand how redirects work, then you also know it is "not possible" to redirect into a new window, because a redirect on the server causes a special HTTP response to be sent to the users browser, the client. The browsers native implementation interprets the special response code and sends the user off to the destination. There's no built-in mechanism or standard for specifying a new window.

Two posts back I discussed a technique you can use to render controls in an order other than how they are physically arranged in the control tree.

When you wrap content with an UpdatePanel, it pretty much takes care of everything for you. But it can't do absolutely everything...

I receive a lot of comments and emails stemming from my series of articles on understanding the nuances of dealing with dynamic controls. It's interesting that so many of these requests revolve around very similar problems.

Part 1: Dynamic vs. Static
Part 2: Creating Dynamic Controls
Part 3: Adding Dynamic Controls to the Control Tree
Part 4: Because you don't know what to render at design time

Going a little off topic today. But with this audience, I bet you are more likely to be interested than if this were a blog about politics.

I've seen this problem a few times now, from a few different developers... including myself. I figure it must have plagued someone else out there too, so hopefully if you read this, if you ever encounter this problem, it wont cost you hours.

A typical ASP.NET AJAX page will contain a fair amount of script references. Sometimes more than you realize, because components you use, such as server controls from the ASP.NET AJAX Control Toolkit, automatically include library scripts that enable their client-side magic. Sometimes you include references explicitly through the ScriptManager's ScriptReferences collection.