Fluent API, many-to-many in Entity Framework Core

Question

I've searched stackoverflow for a proper solution on generating a many-to-many relationship, using EF Core, Code first and Fluent API. A simple scenario would be: public class Person { public Person() { Clubs = new HashSet(); } public int PersonId { get; set; } public virtual ICollection Clubs { get; set; } } public class Club { public Club() { Persons = new HashSet(); } public int ClubId { get; set; } public virtual ICollection Persons { get; set; } } Please correct me if im wrong but I could honestly not find a question that contains an elaborate explanation on how to do this using the described tools. Can anyone explain how this is done? JavaScript questions and answers, JavaScript questions pdf, JavaScript question bank, JavaScript questions and answers pdf, mcq on JavaScript pdf, JavaScript questions and solutions, JavaScript mcq Test , Interview JavaScript questions, JavaScript Questions for Interview, JavaScript MCQ (Multiple Choice Questions)

Answer 1

EF Core 5.0 RC1+ As of EF Core 5.0 RC1, it's possible to do this without an explicit join table. EF Core is able to configure a mapping for the many-to-many relationship shown in your question without requiring you to create a PersonClub type. See What's New in EF Core 5.0, RC1, Many-to-many in the official docs for more information. Previous Versions This is not yet possible in EF Core without using an explicit class for the join. See here for an example of how to do that. There's an open issue on Github asking for the ability to do this without the need for an explicit class, but it has not yet been completed. Using your scenario, the example I linked would recommend the following entity classes: public class Person { public int PersonId { get; set; } public virtual ICollection PersonClubs { get; set; } } public class Club { public int ClubId { get; set; } public virtual ICollection PersonClubs { get; set; } } public class PersonClub { public int PersonId { get; set; } public Person Person { get; set; } public int ClubId { get; set; } public Club Club { get; set; } } The following OnModelCreating would then be used for setup: protected override void OnModelCreating(ModelBuilder modelBuilder) { modelBuilder.Entity() .HasKey(pc => new { pc.PersonId, pc.ClubId }); modelBuilder.Entity() .HasOne(pc => pc.Person) .WithMany(p => p.PersonClubs) .HasForeignKey(pc => pc.PersonId); modelBuilder.Entity() .HasOne(pc => pc.Club) .WithMany(c => c.PersonClubs) .HasForeignKey(pc => pc.ClubId); } Be sure to go to the open issue I linked and voice your frustration if you feel the need. EDIT: The open issue suggests using a simple Select to navigate through this somewhat cumbersome hierarchy. In order to get from a PersonId to a collection of Clubs, you can use SelectMany. e.g.: var clubs = dbContext.People .Where(p => p.PersonId == id) .SelectMany(p => p.PersonClubs); .Select(pc => pc.Club); I can't vouch for whether this is truly a "best practice", but it should certainly do the trick and I think its fair to say it's not overly ugly.