Comments on: ASP.NET AJAX History Part 1: Server-Side

By: AJAX History and ASP.NET AJAX Preview 3 - Asp.Net QA Team

AJAX History and ASP.NET AJAX Preview 3 - Asp.Net QA Team — Tue, 06 Jan 2009 01:18:00 +0000

[…] be a good time to read through the first two parts of Jonathan’s series on ASP.NET AJAX History here and here, as I’m going to assume some basic knowledge about the […]

By: AJAX History and ASP.NET AJAX Preview 3 - Jim Wang's Blog

AJAX History and ASP.NET AJAX Preview 3 - Jim Wang's Blog — Tue, 06 Jan 2009 00:12:59 +0000

[…] be a good time to read through the first two parts of Jonathan’s series on ASP.NET AJAX History here and here, as I’m going to assume some basic knowledge about the […]

By: Greg

Greg — Sun, 04 Jan 2009 01:21:08 +0000

When adding a history point with a NameValueCollection is there a way to specify which comes first? My client wants a certain parameter to come first but I can’t figure out how to force it to do that. For example my current url looks like #&&ResultID=47&CommandID=50 and I need it to be #&&CommandID=50&ResultID=47 instead. I’ve changed the order that I add these to the collection and it doesn’t make a difference. Strangely if I change the CommandID parameter to be CommandID2 then it shows up first, again regardless of the order I put it in the collection.

Thanks in advance.

By: Mike

Mike — Wed, 02 Jul 2008 20:40:00 +0000

@John:

Yeah, it’s a lot of code, and brittle too, with the string keys for history points. It’s major plumbing to get functionality the browser already has (it’s not called a browser for nothing). Basically, using Ajax for full navigation is in many cases overkill.

However, when you are creating a single window web application (think of the Outlook example you often see) than you really need to do this.

By: John

John — Thu, 05 Jun 2008 00:35:49 +0000

This is a great feature/article on asp.net ajax, however I think it’s still a pain in the arse to manually restore a state of a webpage, especially when the page is more than a trivial design with user controls embedded into it and other components you can not manually set. For me, using such a manual restore feature would make my job twice as hard and take twice as long, just to get the same result as a full postback would give me. I’ve come to the conclusions that I’ll only use MS Ajax where I don’t need to restore the page state and just for simple updates within the page. Is anyone else having the same thoughts?

By: Robert

Robert — Tue, 20 May 2008 17:14:54 +0000

What if more than one item is selected?

By: Trevor

Trevor — Mon, 10 Mar 2008 11:41:59 +0000

Thanks for the article, and thanks for not having the entire history of AJAX taking up the first 23 paragraphs of your article. It’s very nice to read an author who gets to the point. Thank you.

By: Julie Lerman

Julie Lerman — Thu, 07 Feb 2008 03:37:43 +0000

I’m with Timothy - sweet and powerful feature. And thanks to the way you have explained it, it makes perfect sense and sounds really easy to use. I’m going to go figure out where I can sneak it into a demo!

By: Timothy Khouri

Timothy Khouri — Thu, 07 Feb 2008 03:06:29 +0000

This is a seriously beautiful feature. When I first heard of the name, I thought of it as being something semi-lame (like a sort of “caching” the requests so that if called again, it would just be a faster response).

But this is really very powerful, and simply amazing. Also, very good article. It describes the technology and makes it fun… I hate lame articles