To convert between some LINQ to SQL objects and DTOs we have created explicit cast operators on the DTOs. That way we can do the following:
DTOType MyDTO = (LinqToSQLType)MyLinq2SQLObj;
This works well.
However when you try to cast using the LINQ .Cast() extension method it trows an invalid cast exception saying cannot cast type Linq2SQLType to type DTOType. i.e. the below does not work
List<DTO.Name> Names = dbContact.tNames.Cast<DTO.Name>()
.ToList();
But the below works fine:
DAL.tName MyDalName = new DAL.tName();
DTO.Name MyDTOName = (DTO.Name)MyDalName;
and the below also works fine
List<DTO.Name> Names = dbContact.tNames.Select(name => (DTO.Name)name)
.ToList();
Why does the .Cast() extension method throw an invalid cast exception? I have used the .Cast() extension method in this way many times in the past and when you are casting something like a base type to a derived type it works fine, but falls over when the object has an explicit cast operator.
The
Cast<>extension method does not apply user-defined conversions. It can only cast to interfaces or within the class heirarchy of the supplied type.User defined conversions are identified at compile time based on the static types involved in the expression. They cannot be applied as runtime conversions, so the following is illegal:
It doesn’t matter whether a UDC exists from
SomeTypetoOtherType– it cannot be applied through a reference of typeobject. Trying to run the above code would fail at runtime, reporting something like:Cast<>()can only perform representation preserving conversions … that’s why you can’t use it to apply user-defined conversions.Eric Lippert has a great article about the behavior of the cast operator in C# – always a worthwhile read.