http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Just curious as to why the ID is a hidden input value rather than a parameter in the URL. I started putting IDs in hidden inputs, but soon realized they really belong in the form's action attribute as part of the action path, since that's how you originally came to the resource. Example: GET: /employee/123/edit POST: /employee/123/do-edit http://ayende.com/3683/reproducing-a-bug#comment13http://ayende.com/3683/reproducing-a-bug#comment13Sun, 09 Nov 2008 23:28:28 GMTI have seen this behavior in past previews as well. I usually get around it by changing my form values to not conflict with route values, but that get's aggravating after a while. http://ayende.com/3683/reproducing-a-bug#comment12http://ayende.com/3683/reproducing-a-bug#comment12Sat, 08 Nov 2008 07:15:47 GMT@Phil, See my comment in Ayende's previous post. I could have sworn this wasn't the way it worked before. In the initial releases if the route didn't have a default value, but it was supplied in the query string then it would take that. Also renaming the parameter isn't always an option. http://ayende.com/3683/reproducing-a-bug#comment11http://ayende.com/3683/reproducing-a-bug#comment11Fri, 07 Nov 2008 21:45:20 GMTAgreed, we'll take a look at it in our next triage meeting. I mentioned it's currently by design, but we will re-evaluate the design. http://ayende.com/3683/reproducing-a-bug#comment10http://ayende.com/3683/reproducing-a-bug#comment10Fri, 07 Nov 2008 19:41:07 GMTAyende - The team noticed that you opened a bug report on CodePlex <<a rel="nofollow external" href="http://www.codeplex.com/aspnet/WorkItem/View.aspx?WorkItemId=2549" title="http://www.codeplex.com/aspnet/WorkItem/View.aspx?WorkItemId=2549">www.codeplex.com/.../View.aspx?WorkItemId=2549 > regarding this issue. I commented on your feedback there to explain the subtleties of the situation a bit more. Thanks for the feedback. :) http://ayende.com/3683/reproducing-a-bug#comment9http://ayende.com/3683/reproducing-a-bug#comment9Fri, 07 Nov 2008 19:37:24 GMTThe first one wasn't a bug report :-) I would say that this is a wrong by design choice to make. Especially when it took me a really long while to figure out what was going on. The route doesn't have an ID parameter, so it should fall back to looking at the request params. Only if it can't find anything, should it try to use the default. As you noted yourself, this doesn't look right. It also mean that something that I do in one place can adversely and non obviously affect in a completely different place. http://ayende.com/3683/reproducing-a-bug#comment8http://ayende.com/3683/reproducing-a-bug#comment8Fri, 07 Nov 2008 19:27:48 GMTOk, it turns out this is by design right now. By convention, if you have a parameter name defined in your route with a default *and* you specify a parameter name to an action method with the same name, we assume you want us to populate that with the route value. The easy fix is to change your default route from id to something else (routeID for example) so that there's no conflict. Otherwise the id in your action method has two meanings. http://ayende.com/3683/reproducing-a-bug#comment7http://ayende.com/3683/reproducing-a-bug#comment7Fri, 07 Nov 2008 19:03:51 GMTThanks! This is a much better bug report than your last one. ;) I confirmed this behavior and it definitely doesn't seem right. I'll circle back with my dev/QA team and figure it out. Thanks! http://ayende.com/3683/reproducing-a-bug#comment6http://ayende.com/3683/reproducing-a-bug#comment6Fri, 07 Nov 2008 18:55:41 GMTActually your issue on codeplex explains this more, for whatever reason, the routing obviously isn't looking at the default values last: one would think: url parameters, qs parameters, form parameters, default parameter (if its convertable) http://ayende.com/3683/reproducing-a-bug#comment5http://ayende.com/3683/reproducing-a-bug#comment5Fri, 07 Nov 2008 17:23:21 GMT@Stephen: the route must look only in the url... it's the action invoker that should probably be smarter to detect which id (the default one retrieved by the url parameter or the one that comes from the HttpRequest) is the right one http://ayende.com/3683/reproducing-a-bug#comment4http://ayende.com/3683/reproducing-a-bug#comment4Fri, 07 Nov 2008 17:23:13 GMTI think this is purely because the routing isn't looking into form values to resolve parameters.. generally routing is resolved from url defined parameters or query string values. http://ayende.com/3683/reproducing-a-bug#comment3http://ayende.com/3683/reproducing-a-bug#comment3Fri, 07 Nov 2008 17:10:32 GMTI guess this is related to your previous post: in this case the action invoker takes the parameter that comes from the url parameter list, which should be (if u are using the default routes) and empty string. So it cannot find an valid int for the Test action. Well... at least it's my guess without doing more tests... try removing the "id" parameter from the route and see what happens http://ayende.com/3683/reproducing-a-bug#comment2http://ayende.com/3683/reproducing-a-bug#comment2Fri, 07 Nov 2008 17:03:19 GMTSubmit to codeplex? http://ayende.com/3683/reproducing-a-bug#comment1http://ayende.com/3683/reproducing-a-bug#comment1Fri, 07 Nov 2008 16:50:18 GMT