svcutil compatibility and minor bugs

[lmagyar]

First, thank you for this great library! It's really terrific!!!

In ConditionalExpressionNode.cs the attribute
[DataMember(EmitDefaultValue = false, Name = "T")] on property
public ExpressionNode Test { get; set; }
conflicts with the same attribute on property ExpressionNode.Type.
Eg. ...Name = "C" as "Condition" could be a solution.

In PropertyInfoNodes.cs there is a

if SERIALIZE_LINQ_WITH_LONG_DATA_NAMES

instead of

if !SERIALIZE_LINQ_OPTIMIZE_SIZE

WARNING: Modifying it breaks backward compatibility with current services, DataContract name changes from "PI" to "PropertyInfoNode"!!!

The "long" DataContract names of MemberNode<> and ExpressionNode<> abstract generic classes should be specified, because svcutil generates "funny" names like ExpressionNodeOfLambdaExpressionQsd8_SODT. And recreates these abstract classes as non-abstract classes during proxy generation (metadata doesn't support abstract). Even when specifying the reference to Serialize.Linq.dll. With "long" DataContract name specified, only one useless non-abstract class should be deleted from the generated proxy.
Eg. [DataContract(Name = "MemberNodeGeneric")] and [DataContract(Name = "ExpressionNodeGeneric")] could be a solution.

[esskar]

thanks for that, i will have a look into that asap

[lmagyar]

I mixed the word DataContract and DataMember in the description above, corrected it now.

[esskar]

does this help?

[lmagyar]

I've added 2 commits.
The first keeps backward compatibility with current servers with ConditionalExpressionNode.Test "short name" T or C.
The second adds support to write sg like node.ToExpression<Func<...>>(new CustomContext()); currently this requires cast or extra typing with custom ConvertToExpression function.
(This is my first contribution to open projects, I'm a newbie on GitHub, I hope I did eg correctly.)

[lmagyar]

I've reverted the first st#pid commit, there is no need to keep backward compatibility, there is no way to send/accept these DataMember(Name = "T") values. Excuse me.

[esskar]

well, you need to trigger a pull request