Hello, I’m just using LLBL for ASP.net core with adapter mode v5.6 I have an issue with using DTO classes, In the projection on a database query, the return the dto filled with the related entities even without adding a path in the query

For example for customer and customerDetail

var metaData = new LinqMetaData(adapter);
    var q = (from c in metaData.Customer
             select c)
            .ProjectToCustomer();
    resultsDTO = q.ToList();

the resultsDTO contains customer and customerDetail for each customer.

My questions are

Why this behavior by default ? How I can switch on/off to allow/prevent related entities without doing in memory projection?

The .ProjectToCustomer() is a helper method that allows you to fill the DTO you built. If you go to definition to that method you can see the projection's tree construction, which is generated by a template. If you want a different behavior you could write your own .ProjectToCustomerSimple() method that removes the child elements, or you could simply not call any method, just do a.ToList() to fill with entities, then you construct the DTO yourself based on the result.

You can read more about DTO projections here in the documentation.