Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

area controllers can't find the view without hardcoding the path? #9

Open
williamsonjake opened this issue Jun 20, 2014 · 1 comment

Comments

@williamsonjake
Copy link

hi there,

i've been using the lowercase-dashed-routes in a project for a while now and it works perfectly (thank you!).

we've just made a change to the project moving some code into an area. i've dropped in the code to XxxAreaRegistration.cs as:

context.Routes.Add("Customer_default", new LowercaseDashedRoute("Customer/{controller}/{action}/{id}", new RouteValueDictionary(new { action = "Index", id = UrlParameter.Optional }), new DashedRouteHandler()));

however, in my controllers i don't seem to be able to use:

return View(viewModel);

as it gives me 'The view 'Index' or its master was not found or no view engine supports the searched locations. The following locations were searched:'

i'm having to specify the path to the view:

return View("~/Areas/Customer/Views/Login/Index.cshtml", viewModel);

am i missing something?!

cheers,

jake

@salarcode
Copy link
Contributor

It is fixed in my fork:
https://github.com/salarkh/lowercase-dashed-route

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants