Tutorials ASP.NET Core Tutorial
ASP.NET Core Project Structure — Complete Guide
ASP.NET Core Project Structure — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of ASP.NET Core Tutorial on Toolliyo Academy.
On this page
ASP.NET Core Tutorial (ShopNest) · Lesson 7 of 100
ASP.NET Core Project Structure
Beginner → Intermediate → Advanced → Professional
Beginner · 1 — Foundations · ~12 min read · Module 1: Introduction & Setup
Introduction
This lesson is part of the beginner section. We explain ASP.NET Core Project Structure slowly, with examples you can copy and run. If something is unclear, read it twice — that is how everyone learns. A new MVC project includes Program.cs (startup), appsettings.json (config), Controllers/, Models/, Views/, wwwroot/ (CSS/JS/images), Properties/launchSettings.json, and a .csproj file. As apps grow, teams add Services/ and Repositories/ folders. When a teammate says “fix the checkout view,” you need to know Views/ vs Controllers/ vs Services/ without guessing. Enterprise teams organize code so five developers do not edit the same file.
ASP.NET Core Project Structure is setup knowledge. Without it, nothing else in ASP.NET Core will run. Spend time here until dotnet run works without errors.
When will you use this?
You need this before writing any ASP.NET Core code — same as installing Visual Studio before opening a project.
- Every .NET backend job expects you to run dotnet new and dotnet run on day one.
- Interviewers often ask you to explain Program.cs and what Kestrel does.
Real-world: Naukri-style job portal API
The Recruitment team building Naukri-style job portal API uses ASP.NET Core Project Structure to know which file to edit when fixing a bug in the checkout API. job seekers and recruiters never see the C# code — they just get a fast, reliable job search and application endpoints.
Production-style code
ShopNest.Web/
Program.cs → startup, DI, middleware
appsettings.json → connection strings, settings
Controllers/ → HTTP handlers (thin)
Models/ → data classes, view models
Views/ → Razor HTML
Services/ → business rules (you add this)
wwwroot/ → static files only
ShopNest.Web.csproj → packages, net8.0What happens in production: In Naukri-style job portal API, getting ASP.NET Core Project Structure right means job seekers and recruiters trust the job search and application endpoints every day.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
ShopNest.Web/
Program.cs → startup, DI, middleware
appsettings.json → connection strings, settings
Controllers/ → HTTP handlers (thin)
Models/ → data classes, view models
Views/ → Razor HTML
Services/ → business rules (you add this)
wwwroot/ → static files only
ShopNest.Web.csproj → packages, net8.0Line-by-line walkthrough
| Code | What it means |
|---|---|
ShopNest.Web/ | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
Program.cs → startup, DI, middleware | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
appsettings.json → connection strings, settings | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
Controllers/ → HTTP handlers (thin) | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
Models/ → data classes, view models | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
Views/ → Razor HTML | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
Services/ → business rules (you add this) | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
wwwroot/ → static files only | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
ShopNest.Web.csproj → packages, net8.0 | Part of the ASP.NET Core Project Structure example — read it together with the lines before and after. |
How it works (big picture)
- Program.cs replaced Startup.cs in modern .NET.
- wwwroot is the only folder browsers access for static files by default.
- Never put secrets in appsettings committed to Git — use User Secrets locally.
Do this on your computer
- Run dotnet new mvc -n ShopNest.Web
- Open each folder and read one file inside.
- Change Views/Home/Index.cshtml heading and refresh the browser.
- Create an empty Services/ folder — you will use it in lesson 21 (DI).
- Read the real-world section and name which part of the app uses this topic.
- Run the example locally with dotnet run and confirm the same behavior.
- Change one value in the example (route, text, or connection string) and predict what will happen before you save.
Experiments — try changing this
- Change a string or route in the example and save — watch the browser or Swagger response update.
- Break the code on purpose (remove a semicolon), read the error message, then fix it.
Remember
Program.cs boots the app. Controllers + Views = MVC. wwwroot holds static assets; Services/ holds business logic.
Common questions
Where do I add new features?
Controller + View per feature, plus a Service class for rules.
What is launchSettings.json?
Dev-only URLs and environment when you press F5 in Visual Studio.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!