ExpressionVisitor.VisitConditional might fail if used in polymorphism about linqkit HOT 1 OPEN

#182 likely solves this for everything more recent then .NET 3.5 as ConditionalExpression.Update explicitly initializes the Type of the new ConditionalExpression to the old Type.

Currently Expression.Condition(test, ifTrue, ifFalse) is used, which (in .NET 3.5) seems to be the only canon way to create ConditionalExpressions and enforces the Type of both expressions to be equal.

• For > .NET 3.5
  • using the bundled ExpressionVisitor (#182),
  • calling ConditionalExpression.Update yourself or
  • using the 'new' (.NET 4.0; .NET Standard 1.0) Expression.Condition(test, ifTrue, ifFalse, type),
    likely each would solve the problem.
• For .NET 3.5 it seems you can only compare types and add converts as needed.

from linqkit.