EF6 Entityvalidationerrors error in filled property

Question

I have a similar problem in two ASP.NET applications with Entity Framework.

When I try to update an entity that already has all the required attributes filled I get an exception from EntityValidationErrors, however that property is described in validarion this filled.

The strange thing is that if I put the breakpoint and check the attributes of the object they are all filled and it does not cause the error.

In one of the applications I am circumventing this problem by making the property receive itself or simply accessing the property and throwing its value in any variable:

ComentariosBlog model = _comentariosBlogNegocios.GetById(idComentatio.Value);

if (model == null)
    return HttpNotFound();

model.Ativo = status.Value;
var teste = model.Publicacao; //<----Contorno
idPost = model.PublicacaoId;
_comentariosBlogNegocios.Salvar(model);

I already have a block of Try Catch that handles this error, the problem is that the object is with all the mandatory properties filled and I have to do a "Gambi" so that it does not generate errors like this in the code above! The simple fact of accessing the property and throwing it in any variable already stops giving error, but I need a more correct solution to this problem, as I said this is only a "Gambi"!

Below is the details of the error that is generated:

In this image we can see that the mentioned property is already filled:

Here is the error message inside the Try catch:

Answer 1

Your Model is wrong. The navigation property:

public virtual PublicacaoBlog Publicacao { get; set; }

Can’t be decorated with [Required] because she will not be saved. What is right is PublicacaoId receive the decoration, because this yes will be saved.

Already this filling out:

var teste = model.Publicacao; //<----Contorno

It attests to how much is wrong with your entire project. It’s easy to see around:

ComentariosBlog model = _comentariosBlogNegocios.GetById(idComentatio.Value);
...
_comentariosBlogNegocios.Salvar(model);

Entity Framework already implements a repository and is NOT required to implement a layer of "services", "business" or anything else, because that’s the role of Controller do. I’ve been writing extensively about this for a long time, so I’ll mention it again:

• Entity Framework DDD Generic Infrarepository
• Work unit (Unit of Work) with repository
• Place where methods of interaction of CRUD with the bank in ASP.NET MVC should be
• problem with update Entity Framework 6
• Application Layer

It is no use to say that "the said MVP is good practice". No, it is not.

• Applying DDD to MVC is not good practice;
• Layer Service in MVC project is not good practice;
• Isolate Controllers and Models in DLL’s different is not good practice;

What you do on the line I marked is make the dynamic proxy turn an object, which correctly fills the foreign key of the object, and therefore saves. To solve, put the [Required] in the right field for him, that is:

[Required]
public int PublicacaoId { get; set; }