Why should you care?

CRUD screens map cleanly to actions: Index, Details, Create, Edit, Delete — interviewers and teammates expect this naming.

See it live — copy this example

Create an MVC project (dotnet new mvc), add the code, and run dotnet run.

public class ProductsController : Controller
{
    public IActionResult Index() => View();

    [HttpGet]
    public IActionResult Create() => View();

    [HttpPost]
    [ValidateAntiForgeryToken]
    public IActionResult Create(ProductViewModel model)
    {
        if (!ModelState.IsValid) return View(model);
        // save product
        return RedirectToAction(nameof(Index));
    }
}

Run Example »

Edit the code and click Run — like W3Schools Try it Yourself.

What happened?

• GET Create shows the empty form.
• POST Create receives form data in model.
• ValidateAntiForgeryToken stops cross-site form forgery.
• RedirectToAction sends user to the list after save.

Try it yourself

1. Add GET and POST Create actions to ProductsController.
2. Build Create.cshtml with a form posting to Create.
3. Submit empty form — observe validation errors.
4. Change text or labels in the example and run again — watch the browser update.
5. Break the code on purpose (remove a semicolon), read the error message, then fix it.

Remember

One URL + HTTP verb = one action method. GET displays forms; POST processes them. Redirect after successful POST prevents duplicate submits.