Entity Core中用AutoMapper映射BookViewModel至Book的关联表问题

Hey Vlad, I’ve been exactly where you are—struggling to map view models to EF Core entities when dealing with explicit join tables like BookAuthor. Unlike older EF versions (or MVC with ICollection<T>), EF Core requires direct handling of the join table entity, so you can’t skip populating BookAuthors entirely. Let’s walk through the solution step by step.

First, Confirm Your Entity & ViewModel Setup #

Assuming your entities look something like this (adjust if your schema differs):

// Book entity
public class Book
{
    public int Id { get; set; }
    public string Title { get; set; }
    // Explicit collection for the join table
    public ICollection<BookAuthor> BookAuthors { get; set; } = new List<BookAuthor>();
}

// Join table entity (required for EF Core many-to-many)
public class BookAuthor
{
    public int BookId { get; set; }
    public Book Book { get; set; }
    public int AuthorId { get; set; }
    public Author Author { get; set; }
}

// BookViewModel (example with author IDs; could also use AuthorViewModels)
public class BookViewModel
{
    public int? Id { get; set; } // Null for new books
    public string Title { get; set; }
    public List<int> SelectedAuthorIds { get; set; } = new List<int>();
}

Configure AutoMapper to Handle the Join Table #

You need to tell AutoMapper to convert the SelectedAuthorIds (or author view models) from your view model into BookAuthor entities. Create a mapping profile:

public class BookMappingProfile : Profile
{
    public BookMappingProfile()
    {
        CreateMap<BookViewModel, Book>()
            // Map basic properties automatically (Title, etc.)
            .ForMember(dest => dest.BookAuthors, opt => opt.MapFrom(src => 
                // Convert each author ID to a BookAuthor instance
                src.SelectedAuthorIds.Select(authorId => new BookAuthor { AuthorId = authorId })
            ));
    }
}

If your view model uses List<AuthorViewModel> instead of IDs, adjust the mapping to pull the ID from each author view model:

.ForMember(dest => dest.BookAuthors, opt => opt.MapFrom(src => 
    src.Authors.Select(authorVm => new BookAuthor { AuthorId = authorVm.Id })
));

Handle Updates: Clean Up Old Associations #

When updating an existing book, you can’t just overwrite the BookAuthors collection directly—you’ll end up with duplicate entries. Instead:

1. Fetch the existing book with its current BookAuthors included
2. Clear the old associations
3. Apply the new mapped associations (or add them manually)

Here’s an example service method:

public async Task UpdateBookAsync(BookViewModel viewModel)
{
    var existingBook = await _dbContext.Books
        .Include(b => b.BookAuthors) // Critical: load existing join records
        .FirstOrDefaultAsync(b => b.Id == viewModel.Id);

    if (existingBook == null)
    {
        throw new KeyNotFoundException("Book not found");
    }

    // Update basic book properties
    _mapper.Map(viewModel, existingBook);

    // Clear old author associations
    existingBook.BookAuthors.Clear();

    // Add new associations (you could also let AutoMapper handle this, but explicit is safer)
    foreach (var authorId in viewModel.SelectedAuthorIds)
    {
        existingBook.BookAuthors.Add(new BookAuthor { AuthorId = authorId });
    }

    await _dbContext.SaveChangesAsync();
}

Key Notes #

• New Books: When creating a new book, EF Core will automatically populate the BookId in BookAuthor when you call SaveChangesAsync()—no need to set it manually.
• Avoid Skipping BookAuthors: If you leave this collection empty, EF Core won’t create any associations between the book and authors, which is almost certainly not what you want.
• Validation: Don’t forget to validate that the SelectedAuthorIds correspond to existing authors in your database before saving!

内容的提问来源于stack exchange，提问作者Vlad