Somewhere in this:

        Dim toReturn As New DataTable
        Dim propertyProjectors As List(Of IEntityPropertyProjector) = EntityFields2.ConvertToProjectors(entities.EntityFactoryToUse.CreateFields)
        entities.DefaultView.CreateProjection(propertyProjectors, toReturn, True, filter)

The order of fields gets reversed. Just a note. Easily fixed on my side with:

        propertyProjectors.Sort(New System.Comparison(Of IEntityPropertyProjector)(Function(x As IEntityPropertyProjector, y As IEntityPropertyProjector) (x.DefaultValueProducer.FieldIndex.CompareTo(y.DefaultValueProducer.FieldIndex))))

but just thought you'd like to know.

Jeff...

Would you please explain in more details what do you mean by reversed?

The resulting datatable has the order of fields reversed so that the field with FieldIndex = 0 in the underlying table is shown last in the datatable.

Note: I think the same thing happens to the order of rows, so that if the entitycollection was sorted ascending, the resulting data comes out sorted descending.

The order of the fields is indeed in reverse order due to the internal algorithm used (to avoid overloaded fields being ignored). Add propertyProjectors.Reverse() below the Dim statement to fix this. I'm on the fence if this is a thing we should release now as a fix, as it might cause problems in user programs... You as a user know that better than us as your software will likely run into problems if you keep the Reverse() statement yourself. Would you say you'd like this as a fix in the current v2.6 builds? I would think you would not want this in between versions, but I'm not sure.

The order of the rows... we'll look into that. (projection of collection. The projection of a datareader is obviously in the order the reader retrieves the rows)

(edit) The order in the rows of the projection of a collection, this is from a view on the collection to a DataTable? As that uses a normal foreach, so in the same order...