Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am new to MVC and still trying got work out the best practices while working on a small MVC doc generator inside our intranet which is developed based on web forms. I was wondering how people are managing the routes for production level sites. I was reading Phil Haack’s article on separating routes but again just wondering how others are doing the work. There must be some good practices around by now which I don’t know of. Tips, links and suggestions will be highly appreciated.
I’m becoming a fan of Attribute-based routing. This particular article by Kevin from the SO team was really helpful and got us kickstarted down this path. For us keeping the routing policies close to the handlers makes maintenance a lot easier and avoids lint from developing. You can also easily unit test the route handling per Controller.