Entity Framework entity model's values empty when running constructor

Question

I'm implementing a POCO in my project that represents a row in my database table. I'd like to modify one of the values in the constructor.

Unfortunately, it seems that the values are populated only after the constructor is run, so there's no way for me to perform my required logic. Is this a bug or by design?

I should probably mention that I'm using Code First.

public partial class CheckpointValue
    {
        [Key, DatabaseGenerated(DatabaseGeneratedOption.Identity)]
        public int Id { get; set; }

        [Column("saljare")]
        public int SalesAgentId { get; set; }

        [Column("volym")]
        public int Value { get; set; }

        [Column("datum")]
        public DateTime Date { get; set; }

        [Column("typ")]
        public string Type { get; set; }


        public CheckpointValue()
        {
            // Values empty... Why haven't they been populated when the constructor is run?
        }
    }

Matías Fidemraizer · Accepted Answer · 2016-01-29 11:45:08Z

1

Unfortunately, it seems that the values are populated only after the constructor is run, so there's no way for me to perform my required logic. Is this a bug or by design?

This is by design. BTW, how you would be able to get these properties already populated during construction-time without providing constructor arguments?.

Maybe you're trying to implement your logic in the wrong place. If you're looking for implementing business rules, domain validation or who knows what, it should be done in another class. For example, your repository would be a good place to do things before returning the requested object.

public CheckpointValue GetById(Guid id)
{
      CheckpointValue checkpointValue = YourDbContext.CheckpointValues.Find(id);
      // Implement here what you wanted in your class constructor...
      return checkpointValue;
}

edited Jan 29, 2016 at 11:45

answered Jan 29, 2016 at 11:37

Matías Fidemraizer

65.1k19 gold badges132 silver badges216 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

silkfire Over a year ago

That's what I suspected. I solved it by implementing the logic in my repository. Really annoying "feature" by design... Thanks again.

Matías Fidemraizer Over a year ago

@silkfire I believe you didn't understand the issue at all. It's by design, but it's how objects work not only in EF but in C# in general. You can't get properties already set before construction-time, and you can't set properties without initializers or constructors.........

Collectives™ on Stack Overflow

Entity Framework entity model's values empty when running constructor

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related