Define Entity Framework relationships using foreign keys only by FluentAPI

Question

Is any way of defining Entity Framework relations using foreign keys only (no virtual properties of reference type) with FluentAPI (data models should not be changed)?

CardDataModel

public class CardDataModel
{
    public int CardId { get; set; }

}

CheckItemDataModel

public class CheckItemDataModel
{
    public int CheckItemId { get; set; }
    public int CardId { get; set; }
}

I'm not sure I understand your question. A navigation property is a virtual property of reference type. — Akos Nagy
– Akos Nagy, Commented Sep 1, 2017 at 11:39
Akos Nagy, no. A navigation property is CardId in CheckItemDataModel. Models shouldn't be changed. Definition should be done by FluentAPI only — Alex Zaitsev
– Alex Zaitsev, Commented Sep 1, 2017 at 11:42
CardId is called a foreign key property. A navigation property is by definition a property that holds a reference to the other of the association. Here's a more detailed description: learn.microsoft.com/en-us/dotnet/framework/data/adonet/… — Akos Nagy
– Akos Nagy, Commented Sep 1, 2017 at 11:52
Can I ask why do you want this? What are the advantages of having a model class/object without Navigation properties? — AndrasCsanyi
– AndrasCsanyi, Commented Sep 1, 2017 at 12:09

Ivan Stoev · Accepted Answer · 2017-09-01 13:47:38Z

9

Yes, it's possible in EF Core. It wasn't in EF6 and below, but now EF Core provides parameterless overloads of HasMany / HasOne which allow configuring such relationship:

modelBuilder.Entity<CardDataModel>()
    .HasMany<CheckItemDataModel>() // <-- note this
    .WithOne()
    .HasForeignKey(e => e.CardId);

answered Sep 1, 2017 at 13:47

Ivan Stoev

208k17 gold badges356 silver badges376 bronze badges

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

Comments

Maritim · Accepted Answer · 2017-09-01 11:27:10Z

-2

You could do this.

public class Card
{
    public int Id { get; set; }
}

public class CheckItem
{
    public int Id { get; set; }
    public int CardId { get; set; }
    public virtual Card Card { get; set; }
}

answered Sep 1, 2017 at 11:27

Maritim

2,1694 gold badges30 silver badges60 bronze badges

6 Comments

DavidG Over a year ago

It seems you missed the part where OP wrote no virtual properties of reference type

Alex Zaitsev Over a year ago

Thanks for your response, but models shouldn't be changed and definition should be done by Fluent API

Maritim Over a year ago

Whoops.. sorry :)

Maritim Over a year ago

May I ask why you don't want them to be virtual @AlexZaitsev?

Maritim Over a year ago

@AlexZaitsev The fact that the property is virtual is not equal to informing the models about the existence of EF. If you were using annotations then I'd agree with you.

|

Collectives™ on Stack Overflow

Define Entity Framework relationships using foreign keys only by FluentAPI

2 Answers 2

Comments

6 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

6 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related