Best Practices for Structuring Large ASP.NET Projects?

Question

Hi everyone,

I’ve been working with ASP.NET for a while now, mostly on small to mid-sized applications. Recently, I started on a larger project and I’m finding it challenging to keep the folder structure and codebase clean as it grows.

Are there any standard practices or architectural patterns you follow to keep large ASP.NET (MVC or Core) projects maintainable and organized?

Would appreciate any tips, examples, or resources you recommend!

Thanks in advance,
Ramesh

Prasad Raveendran · Answer

https://learn.microsoft.com/en-us/dotnet/architecture/modern-web-apps-azure/common-web-application-architectures https://www.youtube.com/watch?v=VKc88NWf4lw https://www.youtube.com/watch?v=1OLSE6tX71Y I recommend first understanding your requirements thoroughly, then selecting the solution carefully. There's always a trade-off to consider

Mahesh Chand · Answer

Clean architecture is recommended. If you have a large project, breaking it down into multiple projects helps, based on layers. Naming projects, folders, classes, and files based on features and entities keeps is clear and clean Keep libraries and services in a different projects and have a separation Encapsulate by features, not types Clean Architecture Project Layout: MyApp.Domain/ +-- Entities/ +-- ValueObjects/ +-- Enums/ +-- Interfaces/ +-- Events/ +-- Exceptions/ +-- Specifications/ MyApp.Application/ +-- Commands/ +-- Queries/ +-- Handlers/ +-- Services/ +-- Interfaces/ +-- DTOs/ +-- Mappings/ +-- Validators/ MyApp.Infrastructure/ +-- Data/ ¦ +-- Configurations/ ¦ +-- Migrations/ ¦ +-- Repositories/ +-- Services/ +-- External/ +-- Caching/ MyApp.Web.API/ +-- Controllers/ +-- Middleware/ +-- Filters/ +-- Models/ ¦ +-- Requests/ ¦ +-- Responses/ +-- Configuration/ +-- Extensions/

Best Practices for Structuring Large ASP.NET Projects?

Answers (2)