News

The 0xFFFFFFFF value (which would seem to be the culprit here) is properly encoded within the signalr::value object and std::vector<signalr::value> collection (i.e. 4294967295.0000000) so it would ...