How to preserve dataannotation in MVC data first approach
up vote
2
down vote
favorite
I am using MVC database first approach and created one .edmx file.
Now my all the tables are available in this model.tt file.
I have also defined some dataannotation on those fields of table.
But What I have noticed that when ever I tried to update this model then value of dataanotation will be lapse.
Any thoughts please.
model-view-controller ef-database-first
add a comment |
up vote
2
down vote
favorite
I am using MVC database first approach and created one .edmx file.
Now my all the tables are available in this model.tt file.
I have also defined some dataannotation on those fields of table.
But What I have noticed that when ever I tried to update this model then value of dataanotation will be lapse.
Any thoughts please.
model-view-controller ef-database-first
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I am using MVC database first approach and created one .edmx file.
Now my all the tables are available in this model.tt file.
I have also defined some dataannotation on those fields of table.
But What I have noticed that when ever I tried to update this model then value of dataanotation will be lapse.
Any thoughts please.
model-view-controller ef-database-first
I am using MVC database first approach and created one .edmx file.
Now my all the tables are available in this model.tt file.
I have also defined some dataannotation on those fields of table.
But What I have noticed that when ever I tried to update this model then value of dataanotation will be lapse.
Any thoughts please.
model-view-controller ef-database-first
model-view-controller ef-database-first
asked Nov 11 at 10:19
chandra prakash kabra
509
509
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Yes it's kinda funny how much you read about annotations but you can't actually use them because they get overwritten.
This is what I found to help me
http://www.ozkary.com/2015/01/add-data-annotations-to-entity.html
also this
https://docs.microsoft.com/en-us/previous-versions/aspnet/ee256141(v=vs.98)
I don't pretend to understand it but here's a join the dots guide.
An example generated EF class looks like this:
public partial class Employee
{
public int Emp_ID { get; set; }
public string Emp_Name { get; set; }
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
Definitely do not edit this.
Instead you create a seperate class file (I called mine metadata.cs and put it in the Models folder) with this in it:
using System;
using System.ComponentModel.DataAnnotations;
using System.ComponentModel;
namespace MyProject.Models
{
[MetadataType(typeof(EmployeeMD))] // new name for your metadata class
public partial class Employee // same name as your EF generated class
{
// Nothing in here
}
internal sealed class EmployeeMD // your metadata class
{
[Required]
[StringLength(50, MinimumLength = 2, ErrorMessage = "Name required")]
public string Emp_Name { get; set; }
[DataType(DataType.Date)]
[DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
}
Your answer really help me and I created metadata classes.
– chandra prakash kabra
Nov 11 at 13:34
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Yes it's kinda funny how much you read about annotations but you can't actually use them because they get overwritten.
This is what I found to help me
http://www.ozkary.com/2015/01/add-data-annotations-to-entity.html
also this
https://docs.microsoft.com/en-us/previous-versions/aspnet/ee256141(v=vs.98)
I don't pretend to understand it but here's a join the dots guide.
An example generated EF class looks like this:
public partial class Employee
{
public int Emp_ID { get; set; }
public string Emp_Name { get; set; }
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
Definitely do not edit this.
Instead you create a seperate class file (I called mine metadata.cs and put it in the Models folder) with this in it:
using System;
using System.ComponentModel.DataAnnotations;
using System.ComponentModel;
namespace MyProject.Models
{
[MetadataType(typeof(EmployeeMD))] // new name for your metadata class
public partial class Employee // same name as your EF generated class
{
// Nothing in here
}
internal sealed class EmployeeMD // your metadata class
{
[Required]
[StringLength(50, MinimumLength = 2, ErrorMessage = "Name required")]
public string Emp_Name { get; set; }
[DataType(DataType.Date)]
[DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
}
Your answer really help me and I created metadata classes.
– chandra prakash kabra
Nov 11 at 13:34
add a comment |
up vote
1
down vote
accepted
Yes it's kinda funny how much you read about annotations but you can't actually use them because they get overwritten.
This is what I found to help me
http://www.ozkary.com/2015/01/add-data-annotations-to-entity.html
also this
https://docs.microsoft.com/en-us/previous-versions/aspnet/ee256141(v=vs.98)
I don't pretend to understand it but here's a join the dots guide.
An example generated EF class looks like this:
public partial class Employee
{
public int Emp_ID { get; set; }
public string Emp_Name { get; set; }
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
Definitely do not edit this.
Instead you create a seperate class file (I called mine metadata.cs and put it in the Models folder) with this in it:
using System;
using System.ComponentModel.DataAnnotations;
using System.ComponentModel;
namespace MyProject.Models
{
[MetadataType(typeof(EmployeeMD))] // new name for your metadata class
public partial class Employee // same name as your EF generated class
{
// Nothing in here
}
internal sealed class EmployeeMD // your metadata class
{
[Required]
[StringLength(50, MinimumLength = 2, ErrorMessage = "Name required")]
public string Emp_Name { get; set; }
[DataType(DataType.Date)]
[DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
}
Your answer really help me and I created metadata classes.
– chandra prakash kabra
Nov 11 at 13:34
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Yes it's kinda funny how much you read about annotations but you can't actually use them because they get overwritten.
This is what I found to help me
http://www.ozkary.com/2015/01/add-data-annotations-to-entity.html
also this
https://docs.microsoft.com/en-us/previous-versions/aspnet/ee256141(v=vs.98)
I don't pretend to understand it but here's a join the dots guide.
An example generated EF class looks like this:
public partial class Employee
{
public int Emp_ID { get; set; }
public string Emp_Name { get; set; }
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
Definitely do not edit this.
Instead you create a seperate class file (I called mine metadata.cs and put it in the Models folder) with this in it:
using System;
using System.ComponentModel.DataAnnotations;
using System.ComponentModel;
namespace MyProject.Models
{
[MetadataType(typeof(EmployeeMD))] // new name for your metadata class
public partial class Employee // same name as your EF generated class
{
// Nothing in here
}
internal sealed class EmployeeMD // your metadata class
{
[Required]
[StringLength(50, MinimumLength = 2, ErrorMessage = "Name required")]
public string Emp_Name { get; set; }
[DataType(DataType.Date)]
[DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
}
Yes it's kinda funny how much you read about annotations but you can't actually use them because they get overwritten.
This is what I found to help me
http://www.ozkary.com/2015/01/add-data-annotations-to-entity.html
also this
https://docs.microsoft.com/en-us/previous-versions/aspnet/ee256141(v=vs.98)
I don't pretend to understand it but here's a join the dots guide.
An example generated EF class looks like this:
public partial class Employee
{
public int Emp_ID { get; set; }
public string Emp_Name { get; set; }
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
Definitely do not edit this.
Instead you create a seperate class file (I called mine metadata.cs and put it in the Models folder) with this in it:
using System;
using System.ComponentModel.DataAnnotations;
using System.ComponentModel;
namespace MyProject.Models
{
[MetadataType(typeof(EmployeeMD))] // new name for your metadata class
public partial class Employee // same name as your EF generated class
{
// Nothing in here
}
internal sealed class EmployeeMD // your metadata class
{
[Required]
[StringLength(50, MinimumLength = 2, ErrorMessage = "Name required")]
public string Emp_Name { get; set; }
[DataType(DataType.Date)]
[DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
public Nullable<System.DateTime> Commencement_Date { get; set; }
}
}
answered Nov 11 at 11:42
Nick.McDermaid
11.5k32554
11.5k32554
Your answer really help me and I created metadata classes.
– chandra prakash kabra
Nov 11 at 13:34
add a comment |
Your answer really help me and I created metadata classes.
– chandra prakash kabra
Nov 11 at 13:34
Your answer really help me and I created metadata classes.
– chandra prakash kabra
Nov 11 at 13:34
Your answer really help me and I created metadata classes.
– chandra prakash kabra
Nov 11 at 13:34
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53247755%2fhow-to-preserve-dataannotation-in-mvc-data-first-approach%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown