HierarchyId serialized in an invalid format which can't be deserialized

[dotmorten]

HierarchyId serialized in an invalid format which can't be deserialized

[dotMorten]

In that case we need to find what id got serialized and validate that they can deserialize again.

TBH I don't know anything about these ids. It was a community contribution and has been maintained by external devs so the more info you can find the greater chance it can get resolved

[ppasieka]

@AndyBates6668 fix for this issue is in #55

[Torvin]

Here's a test that passes for full framework and fails in .net core:

public void TestWrongSerialization()
{
    var h = SqlHierarchyId.Parse("/3.1/");
    var ms = new MemoryStream();
    h.Write(new BinaryWriter(ms));
    var value = ms.ToArray();
    CollectionAssert.AreEqual(value, new byte[] { 0x81, 0x60 });
}

Looks like it's fixed in #55

[dotMorten]

A small testmethod the shows the problem would be awesome. If you clone the repo and add it to the test class, the test should pass for .net framework (as that runs against official libraries) and fail against .net core.

[AndyBates6668]

As I say I'm not sure what the string was that generated that binary data. The HierarchyId class obviously generated it but it fails to deserialize in both .net framework and the .net core builds. I'm doing some more digging so will report what I turn up. Is it possible to decode the binary data or at least identify what the hierarchy id is (or even part of it)?

[AndyBates6668]

As I say we're using the library and the test team caused invalid serialised hierarchy identifiers to be generated and dropped into the SQL database. I'll see if I can reproduce and get the source identifiers for these or do some more digging to see how they were generated.

[AndyBates6668]

There are 2 fixes I'm interested in seeing released. This plus the GetDescendants issue. Do we know when a pre-release/release can be completed for further testing? Thanks Andy

[AndyBates6668]

What is the process for the PRs for resolving issues 46 and this issue to be completed? We're using the code and seeing this issue more frequently so would like to get the fixes in place. Many thanks Andy

[dotMorten]

The process is to download the source code and build it yourself - at least until I don't feel burnt out and again have the energy to dig into these PRs, test them, and release a new version.

[Torvin]

@dotMorten thank you for your hard work. If it helps, I did exactly that - downloaded the code from PR #55 branch and using it in production right now and everything is working fine so far

[dotMorten]

Try v1.3.0 that have the #55 code.