A few days ago I published the latest ASP.NET Core Demystified [https://www.exceptionnotfound.net/tag/asp-net-core-demystified/] post which was all about Razor Pages [https://www.exceptionnotfound.net/asp-net-core-demystified-razor-pages] and demonstrated how to build an app using them. In the process of writing that post, I realized that I
ASP.NET Core 2.0 was released just a few weeks ago, and included a new feature that may be the biggest single addition to ASP.NET Core since it was announced: Razor Pages! Come along with me as we figure out what Razor Pages are for, how they are
We can set a custom default landing page for our ASP.NET Core Razor Pages apps! Here's how.
Next up in our ASP.NET Core Demystified [https://www.exceptionnotfound.net/tag/asp-net-core-demystified/] series, we will discuss and demo a whole bunch of classes which implement the IActionResult interface [https://docs.microsoft.com/en-us/aspnet/core/api/microsoft.aspnetcore.mvc.iactionresult] and inherit from the corresponding ActionResult class [https:
For the next part of my ASP.NET Core Demystified [https://www.exceptionnotfound.net/tag/asp.net-core-demystified] series, we're sticking with MVC and explaining how the model binding system works. As with all my Demystified series posts, there's a sample project over on GitHub [https://github.com/exceptionnotfound/AspNetCoreModelBindingDemo] which