Entity Framework Code-first (9.10): dataannotations-notmapped Attribute

dataannotations-notmapped Attribute:

notmapped attribute can is applied to properties of a class. Default Code-first Convention creates a column for all the properties which includes getters and setters. notmapped attribute overrides this default convention. You can apply notmapped attribute to a property which your do not want to create a column in a database table for.

Consider the following example.

usingSystem.ComponentModel.DataAnnotations; Public classstudent{ PublicStudent () {} Public intStudentID {Get;Set; }  Public stringStudentname {Get;Set; } [Notmapped] Public intAge {Get;Set; }}

As you can see in the above example, notmapped attribute are applied to the age property of the Student class. So, Code first would not be create a column to store age information in the Student table as shown below.

Code-first also does not create a column for a property which does does have either getters or setters. Code-first won't create columns for FirstName and an in the following example.

usingSystem.ComponentModel.DataAnnotations; Public classstudent{ PublicStudent () {}Private int_age =0;  Public intStudentID {Get;Set; }  Public stringStudentname {Get;Set; }  Public stringFirstName {Get{returnStudentname;} }     Public stringAge {Set{_age =value;} }    }

Entity Framework Code-first (9.10): dataannotations-notmapped Attribute