Linq, many-to-many relationship in EF?

Question

SQL

There is a database implemented many-to-many relationship through the intermediate table ProductRepo.

After screwing the database into the project through EF, the database comes out without an intermediate table with a many-to-many relationship.
With such a query to the database:

Select Product.Name, Product.Price, Product.Count, Repository.Name
from Product, Repository, ProductRepo 
where Product.Id = ProductRepo.IdProduct AND Repository.Id = ProductRepo.IdRepository

I get the result

that I need.
But, when I try to get the same result through LINQ, I get trouble.
There was already a similar question and it was advised to do this:

var query = db.Products.Include(x => x.Repositories).ToList();

But it gives the following error:

With this request:

var query = db.Products.Include("Repositories").ToList();

and passing the result to the view is already closer to the truth, but:

But in debugging it shows that there is a property I need:

Now the question is: how to write a LINQ query correctly to get a similar one

Select Product.Name, Product.Price, Product.Count, Repository.Name
from Product, Repository, ProductRepo 
where Product.Id = ProductRepo.IdProduct AND Repository.Id = ProductRepo.IdRepository

or how to pull the property I need:

Answer 1

In general, there are several options. We can manually add the desired linking table to the context.
Or do something like this:

var data = db.Products.Include("Repositories");
var values = new List<ProductWithRepoDTO>();

foreach(var record in data)
{
    var reposArray = record.Repositories.Select(x=>x.Name).ToArray();
    var reposString = string.Join(",", reposArray);
    
    values.Add(new ProductWithRepoDTO
    {
        Id = record.Id,
        Name = record.Name,
        Cound = record.Count,
        Price = record.Price,
        Repository = reposString 
    });        
}
//дальше работать с values

The second approach, in my opinion, is more correct, because. you are no longer working with a domain model, but with a view model that already contains data that is convenient for displaying .

Answer 2

But it gives this error:
Connect
using System.Data.Entity;