I feel like it would be usefull to post a quick patch
for  "Deserialising a null string produces a
run-time error" i've posted earlier.
One working with VisiBroker 4.x might at some point
discover that IIOP.Net is raising an overflow exception
when [vbroker.orb.enableNullString=true] feature of VB
is used. This feature allows string values, which
represent null, to have a zero length. However,
IIOP.NET assumes a string value to have at least one
byte, thus causing an overflow during deserialisation.
This patch implements a check before deserialising a
string value, and returns null on zero-length string.