.NET Standard supporting about linqspecs HOT 3 CLOSED

Perhaps it makes sense to wait for .NET Standard 2.0

from linqspecs.

Maybe remove SpecSerizlization ? In 2k17 it's looks like legacy code

from linqspecs.

@ZOXEXIVO
I thought about removing of serialization. But some developers need to transfer specifications to a server. So I think that in some kind serialization is needed. In addition, if we remove serialization it may be a serious violation of backwards compatibility for some users of LinqSpecs.

Unfortunately now AdHocSpecification serialization does not work satisfactorily (serialization of some elements of expression tree does not supported, for example, you can not serialize an expression containing null).

I see two solutions:

1. Correct the serialization of expression trees in LinqSpecs.
2. Use other NuGet packages for expression tree serialization.

I prefer the first option, and I'm trying to implement it gradually. Unfortunately this turned out to be a nontrivial task, and I have very little free time now, so the work is slow, I do not know how long it will take.

But why did you say that serialization looks like legacy code?

from linqspecs.