In the RC, we changed our helpers which generate URLs to generat relative paths instead of absolute paths. We've noticed this has broken a lot of scenarios we did not anticipate, such as certain Ajax partial view scenarios.

Also in the RC, we made a change to RouteUrl and RouteLink that has introduced a regression bug in some scenarios. If this has affected you, let me know. We're trying to get a sense of how many people are affected by these regressions. 

We are definitely looking into this and considering several options. It will help us to know how many people are affected.

Yes, I'm experiencing this issue. When rendering partial views, the form actions sometimes aren't correct and also, Html.ActionLink() and Url.Content() don't behave properly.
Especially when the controller executes its default action (Index) that doesn't show up in the address bar, things go wrong with the partial request.

This is a 100% showstopper (unless there is a hidden switch somewhere that turns off relative urls :)).

After reading all the posts here lately I'm too scared to change to RC1.  If I get time I'll try upgrading my current project and see what happens

I had an issue where the relative URL from BeginForm caused a problem using the jQuery ajaxForm plugin. I was able to work around it by providing the URL as an option in the plugin, but this defeats the purpose for using BeginFrom.

I have a small/medium size project (6 controllers 17 views) and update to RC1 in about 2 hours with no major issues.  A few of the changes like SetAttemptedValue and BindModel took me a few minutes to figure out but seem to be working now.  I didn't run into the issues you described.  I guess I should note that I am not using AJAX anywhere in this app yet.

Sadly recent url generation code broke most of ajax calls in the project I am working on, as most of them were called on different controller, because they originated from controls placed within master pages.

The good news is that every single dynamic url I generated was from my own extension methods, as I like to actually encode urls on the way for xhtml confirmance, if i inject them directly into href attribute. So solution was to pass resulting url strings via additional method which converted them back to absolute in case incoming request was async Ajax request.

The bad news is that now I wont ever be able to use HtmlHelper extensions for generation elements which include urls in views I am aware that could be rendered asynchronously, so in general all views as otherwise it would cause total mess, leaving me only with my own UrlHelper extensions.

Yep, killed all of the views in my project.  I am using Ajax w/partial views (partial page replacement).

Definitely got me.

See my post over on StackOverflow  http://stackoverflow.com/questions/491704/asp-net-mvc-routing-issue

 Yep, I too am impacted from this change, and we greatly need it to be fixed, as we are halfway through our project and it is critical to have this working. My problem is addressed here:

http://forums.asp.net/p/1377815/2902614.aspx#2902614

Thanks.

 Regards,

 Winston

Ditto

 Hi Phil, This is a problem for me.

 <%= Url.Action<ReportController>(controller => controller.VehicleLogReport(null)) %>

writes /Report/VehicleLogReport and is fine.

 <%= Url.Action("VehicleLogReport", "Report") %>

 writes VehicleLogReport and breaks my site. 

 As you suggested this is an ajax partial view scenario.

They released a RC Refresh tonight which rolls back the changes to relative URLs. You should grab that and you guys should be set. Same download link as before.

Note, at the moment, the refresh MSI hasn't propagated to all download servers. So you might inadverdently download the old one.