Almost every day one of my teammates will come to me with a "bug" or problem they discovered and want to know if we should fix it as part of the next deployment, or wait for the QA department (whom we jokingly refer to as the bug hunting team [http:
Entity Framework Code-First includes a new feature for maintaining database changes in code files: Migrations. Migrations are code files that describe what changes were made to the database schema at different points in time. You create the migrations when you need them, and the code will use those files (and
Footsteps echo through the empty hallway as you stride, coffee in hand, toward your study. You cross the threshold, briefly pausing to flick on the overhead lights, and the laptop on the center table stares back at you, the schematics gleaming on its too-bright screen. Setting the cup down, you
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