How to Add a read-only Property to Database first Entity Framework 6 metadata

If the FullName column doesn't exist in the database table which means no property FullName exists in your EF model Student class you'll get this error.

1. I doubt you can achieve what you want using metadata-approach. But you can modify the way your properties are rendered in a view. If the following is your EF model class:

   public partial class Student
   {   
     public string FullName 
     {             
       get;
       set;
     }
   }
   

2. Then create another partial class called Student and place it in the same assembly(folder) but in a different file with a different file name. it'd look like this:

   [MetadataType(typeof(StudentMetadata))]
   public partial class Student
   {
   }
   
   public class StudentMetadata
   {
       [Display(Name = "Full Name")]
       public string FullName { get; set; }          
   } 
   

then if you render your EF model Student class in a view

@model Models.Student
@Html.DisplayForModel()

The name of the property will be displayed the way you wanted:

If you want to prevent user from editing the field by making it readonly, you may want to use this

 @Html.TextBoxFor(m => m.FullName, new{ disabled = "disabled", @readonly = "readonly" })

I am not sure how to achieve the same effect with Html.EditorForModel

Alternatively if you still want a property FullName made up of other two properties FirstName and LastName I'd try:

1. Your EF model class:

   public partial class Student
   {
    public string FirstName
    {
        get; set;
    }
   
    public string SecondName
    {
       get; set;
    }
   

   }

2. Class extending Student class:

   public class StudentChild : Student
   {
   
   [Display(Name="User name")]
   public String FullName
   {
       get { return FirstName + ", " + SecondName; }
   }
   

   }

3. Then in your view:

   @model StudentChild
   
   @Html.DisplayForModel()
   

I am not sure the latter is the perfect approach as in the case that your underlying database schema changes then you need to modify your child class.