Another problem is:
Repro:
1. Don't use routing
2. Do something like ${UrlHelper.Link("A Link", { @action:"hi" })}
when you are at http://localhost/rea/roller/index
3. Link generated: <a href="/rea/roller/hi">A link</a>
4. Use routing, like described in my last e-mail, default "index"
5. Do same link at same location at http://localhost/rea/roller/index
(technically you'd see ---/rea/roller in the bar)
6. Link generated: <a href="/hi">A link</a>
Problem:
This breaks this aim: Change MR internals to always rely on the routing
infrastructure, in a way that the standard behavior is backward compatible
with previous versions. In other words, an application that does not
register any routing definition should behave as if there is two
definitions: one for area/controller/action and other for controller/action.
From: http://using.castleproject.org/display/MR/Routing+Spec
Workaround: use full syntax with area, controller in dictionary, but this
should be checked in the helper against the controller context like it is if
I don't use routing, and, with routing, default to using the current
location, appending nothing to the current location, in this case, to
maintain the aim.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
