I just deployed the MVC4.NET 4.0 application for my web host, for "detailed" testing. Non -aretic routes work fine, for example. my
@Html.ActionLink("Register as a Client", "Register", "Account", new { registrationType = "Client"}, null)
the link works fine, and the link opens the correct page. However, with reference to an area-based action, for example:
@Html.ActionLink("Authors", "Index", "Home", new { Area = "Author", registrationType = "Author" }, null)
the link actually displayed in the browser is missing an action and controller, i.e.
http:
It may be worth noting that the css MVC4 linking function did not work after deployment, and I returned to using classic-style links in separate style sheets.
MAYBE RELATED: My question is: Why is the unmodified template code in my MVC4 application trying to double-register areas?
JUST IN: Removing the default action from the default route route mappings for Runet solved this problem. There was no default controller in the VS2012 template template.
asp.net-mvc asp.net-mvc-4 asp.net-mvc-routing asp.net-mvc-areas
ProfK Jul 17 '12 at 21:19 2012-07-17 21:19
source share