…pected by switch statements and if/else blocks

…lue).

This is something I agreed on with Jeremy Kuhne a while ago, but missed it.

…the value of the Id in explicit way

…fo (Length property is longer present in this type)

… a place where it's not valid

… complete, but increases the amount of code that needs to be reviewed

…vided in a place where it's not valid

… is always illegal to parse it and every switch needed to take this into account.

Now we reject those values at parse time and don't need to handle them later.

- In case of BinaryArray (NRBF 2.4.3.1):
 "If the BinaryTypeEnum value is Primitive, the PrimitiveTypeEnumeration
 value in AdditionalTypeInfo MUST NOT be Null (17) or String (18)."
- In case of MemberPrimitiveTyped (NRBF 2.5.1):
 "PrimitiveTypeEnum (1 byte): A PrimitiveTypeEnumeration
 value that specifies the Primitive Type of data that is being transmitted.
 This field MUST NOT contain a value of 17 (Null) or 18 (String)."
- In case of ArraySinglePrimitive (NRBF 2.4.3.3):
 "A PrimitiveTypeEnumeration value that identifies the Primitive Type
 of the items of the Array. The value MUST NOT be 17 (Null) or 18 (String)."
- In case of MemberTypeInfo (NRBF 2.3.1.2):
 "When the BinaryTypeEnum value is Primitive, the PrimitiveTypeEnumeration
 value in AdditionalInfo MUST NOT be Null (17) or String (18)."