Comments on: jQuery for Asp.net MVC preview 3

By: Link List 20080617 | Guru Stop

Link List 20080617 | Guru Stop — Sat, 13 Feb 2010 22:42:33 +0000

[...] · jQuery for Asp.net MVC preview 3 [...]

By: Chris van de Steeg

Chris van de Steeg — Thu, 26 Jun 2008 11:56:09 +0000

@Roger: that’s only the case if you have the option to do catch all incoming requests (wildcard mapping). If you need .aspx in your url to go to asp.net (eg because your hosting company requires you), you need to exclude the Contents folder yourself

By: Roger Chapman

Roger Chapman — Thu, 26 Jun 2008 11:49:20 +0000

You mentioned ignoring the Contents folder in your routes; this is not required.
In the new routing engine, if the file being requested exists on the folder structure (as the Contents folder) it will be automatically ignored by the routing engine.

By: Nick Berardi

Nick Berardi — Wed, 18 Jun 2008 21:02:25 +0000

Cool Chris,

Let me know if you need any help.

By: Rodrigo

Rodrigo — Wed, 18 Jun 2008 13:47:31 +0000

The online demo is not working.

By: Chris van de Steeg

Chris van de Steeg — Tue, 17 Jun 2008 18:32:29 +0000

@Nick: Excellent suggestion! I’m converting it right now. Thanks alot

By: Link List 20080617 - Guru Stop

Link List 20080617 - Guru Stop — Tue, 17 Jun 2008 15:21:40 +0000

[...] · jQuery for Asp.net MVC preview 3 [...]

By: Nick Berardi

Nick Berardi — Tue, 17 Jun 2008 14:21:19 +0000

Hi Chris, I like where this is going. I just have a few concerns about why you require a Controller to be inherited. You can accomplish the same results by using an Attribute. I have created an attribute that allows you to simple specify [Service] at the method or controller level that will automatically serialize the ViewData on output if JSON, JSONP, or XML is requested.

http://code.google.com/p/coderjournal/source/browse/trunk/ManagedFusion/Source/Web/Mvc/ServiceAttribute.cs

I also created my own serializer that works with anonymous types. I was having trouble with the JavaScriptSerializer that the Json ActionResult uses.

contact me if you have any troubles.

By: Chris van de Steeg

Chris van de Steeg — Mon, 16 Jun 2008 11:04:13 +0000

@Jake: the meta:ajaxtarget is used to determine where to put the loaded ajax-content (which div). I used this so it would be easy to create your own anchor-tags without having to using the HtmlHelpers.

I agree, it should be valid xhtml. I’m not yet sure if using the rev attribute would be the best way to go though. We’d be using it the wrong way then, since it should indicate a relation between the current and the next page.

By: Jake Scott

Jake Scott — Sun, 15 Jun 2008 21:35:35 +0000

Hi Chris, I used the same technique when preview 3 came out and it works really well.

I have a small suggestion and that would be to use the rev attribute of the a tag to define the target instead of the meta:ajaxtarget=”#maincontent”. Its just that it makes development so much easier when developing your pages with green validation lights

http://reference.sitepoint.com/html/a/rev

Does the ajax history stuff you included rely on this attribute?