MVC logic

Question

I have started learning MVC, some tutorials use entity framework with it, another not, can you make some points on MVC logic and give a simple example for developing MVC app with connect to sqlserver

Tuhin Paul · Answer

Learning Model-View-Controller (MVC) is a significant milestone in software architecture. To clarify your confusion about Entity Framework (EF): EF is not MVC. MVC is a design pattern for the UI, while EF is a tool for data access.

Darshan Adakane · Answer

Hello Suzan MVC (Model-View-Controller) is a design pattern that separates an application into three parts. Model ? Represents data and business logic (e.g., classes + DB interaction) View ? UI layer (Razor .cshtml) used to display data Controller ? Handles HTTP requests, interacts with Model, and returns View Request Flow User ->Controller -> Model -> Database-> View -> User Entity Framework vs Without EF With EF Core (Recommended) ORM (Object Relational Mapper) No need to write SQL manually Faster development, cleaner code Without EF (ADO.NET) Manual SQL queries More control but more boilerplate code Simple MVC + SQL Server Example (EF Core) Model public class Employee { public int Id { get; set; } public string Name { get; set; } public string Department { get; set; } } DbContext public class AppDbContext : DbContext { public AppDbContext(DbContextOptions options) : base(options) { } public DbSet Employees { get; set; } } Controller public class EmployeeController : Controller { private readonly AppDbContext _context; public EmployeeController(AppDbContext context) { _context = context; } public IActionResult Index() { var data = _context.Employees.ToList(); return View(data); } [HttpPost] public IActionResult Create(Employee emp) { _context.Employees.Add(emp); _context.SaveChanges(); return RedirectToAction("Index"); } } Key Points MVC ensures separation of concerns Controllers should be lightweight EF Core simplifies DB operations Use Dependency Injection for DbContext Use MVC + EF Core for most applications to keep code clean, maintainable, and scalable, while ADO.NET is useful when fine-grained SQL control is required. Hope this answer helps. If yes, please mark as accepted answer.

MVC logic

Insert Link

Embed YouTube Video

Table Options

Insert Image

Answers (2)