From the course: ASP.NET MVC: Building for Productivity and Maintainability
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Understanding the feature folders approach
From the course: ASP.NET MVC: Building for Productivity and Maintainability
Understanding the feature folders approach
- [Instructor] Pretty much every ASP NET MVC tutorial in existence, tells you that you need to put your views in your applications views folder, and that you should put your controllers in a folder named controllers. And while you don't actually need to put your controllers in the controllers folder, you can actually put them anywhere in the project that you like, the advice regarding where to put your views is correct because the default ASP NET MVC view engine will only work if you put them in the views folder, because that's the only place it will look for them. Due to that advice and the restriction imposed by the framework, the folder structure of the vast majority of ASP NET MVC applications ends up looking like this. It's a structure that's based on technical relationships, as opposed to logical relationships. In other words, other than the fact that the controller classes are controllers, the reality is that they actually have very little to do with each other, and more to do…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.