Edge case of an edge case reported under https://github.com/BHoM/BHoM_Engine/issues/3343 - if a property is removed with MessageForDeleted, its parent type will version correctly only if there is exactly one matching type for it.
However, it may happen that there is more than one assembly containing that particular type (which currently happens only with Revit stuff, where we have version-specific assemblies), and then the type is not found, leading to the object being deserialised to CustomObject.
Description:
Edge case of an edge case reported under https://github.com/BHoM/BHoM_Engine/issues/3343 - if a property is removed with
MessageForDeleted
, its parent type will version correctly only if there is exactly one matching type for it.However, it may happen that there is more than one assembly containing that particular type (which currently happens only with Revit stuff, where we have version-specific assemblies), and then the type is not found, leading to the object being deserialised to
CustomObject
.