Closed aienabled closed 7 years ago
By the way, it's very smelly that the method MetaType.ResolveTupleConstructor
is actually used not only to resolve the tuple constructor, but for other types as well.
Thank you, I'm going to add the support for .NET 4.7 later (and may be Core?), I even don't have VS 2017 installed yet...
By the way, it's very smelly that the method MetaType.ResolveTupleConstructor is actually used not only to resolve the tuple constructor, but for other types as well.
It is used for AutoTuple feature where you can make your own tuple type and it will be auto-detected. As far as I remember tuples are expected to use only readonly properties - this is why it doesn't detect ValueTuple which uses writeable fields.
By the way, it's very smelly that the method MetaType.ResolveTupleConstructor is actually used not only to resolve the tuple constructor, but for other types as well.
It is used for AutoTuple feature where you can make your own tuple type and it will be auto-detected. As far as I remember tuples are expected to use only readonly properties - this is why it doesn't detect ValueTuple which uses writeable fields.
In that case - all right. I just was confused by the name of the method. Isn't it should be ResolveAutoTupleConstructor
then?
I will pull your commits to check the ValueTuple
serialization right now.
Yes, it works properly. Thanks!
There is no support for new
ValueTuple
(de)serialization. I've hacked my solution based ontype.FullName
check (where there are checks forSystem.Tuple
) and commenting out this code: