Now that we've created a Code-First model using Attributes [http://www.exceptionnotfound.net/entity-framework-for-beginners-a-code-first-model-using-attributes] , let's walk through the other manner by which we can create a model: FluentAPI. The Model Once again, we will be using the same CourseCatalog model: To start off, let's create the classes necessary to represent
In previous posts we have created a database-first model [http://www.exceptionnotfound.net/entity-framework-for-beginners-creating-a-database-first-model/] , created a model-first model using an EDMX [http://www.exceptionnotfound.net/entity-framework-for-beginners-creating-a-model-first-model/] , and created a code-first model from an existing database [http://www.exceptionnotfound.net/entity-framework-for-beginners-creating-a-code-first-model-from-a-database] . In this post, we will create a co
In previous posts we've explored creating a database-first model [http://www.exceptionnotfound.net/entity-framework-for-beginners-creating-a-database-first-model/] and creating a model-first model [http://www.exceptionnotfound.net/entity-framework-for-beginners-creating-a-model-first-model/] . Both of those designs used the same thing: an EDMX file. In order to use that file, we had to use a designer. But what if
In my Internal Web Tools group at my day job, we regularly deal with end users who are rather, shall we say, insistent that they need a particular feature on an app we are building for them. When we ask them why they need that feature, their responses generally includes
I was a little hesitant about the new Tag Helpers feature coming out with ASP.NET Core and ASP.NET MVC 6 when I last wrote about it [http://www.exceptionnotfound.net/tag-helpers-in-asp-net-5/], but a few recent updates have totally changed my mind. These things are going to be awesome.