tag:blogger.com,1999:blog-13073408.post2167985607181761198..comments2008-04-18T23:39:02.503-04:00Peter Lanoiehttp://www.blogger.com/profile/11480942345027154915noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13073408.post-27906596834707335322008-04-18T23:39:00.000-04:002008-04-18T23:39:00.000-04:00I attended a user group presentation about the ASP.NET MVC framework. MVC makes use of "RESTfulness" to my understanding. I asked the presenter about how ASP.NET gets the requests from IIS as the URLs are not .aspx pages. He said that the application's configuration (web.config) handles this in IIS7 automatically. We have to manually create ISAPI mappings for IIS6.<BR/><BR/>That may all be irrelevant because I have no idea how RESTful apps are constructed in ASP.NET. But I guess my point in blabbering about the MVC is that I imagine they have some solution to the problem I describe. Simply making the resolved paths root relative instead of page relative should solve the problem. I'd be delighted to find that there already exists a setting for this.Peter Lanoiehttp://www.blogger.com/profile/11480942345027154915noreply@blogger.comtag:blogger.com,1999:blog-13073408.post-87109008540369080042008-04-18T16:21:00.000-04:002008-04-18T16:21:00.000-04:00Hi Peter,<BR/><BR/>Interesting problem, and TBH, I can offer nothing in the way of the solution.<BR/><BR/>However, the path style looks very much like that of a RESTful website yes? Does looking at how RESTful websites are created using .NET offer any leads?robchttp://robc.myvidoop.com/noreply@blogger.com