Fix for updating assembly version in persisted type strings. Schema is updated when using a different VelocityDB assembly version compared to version used by prior update transaction. This is unfortunate but currently required because current .Net class loader is using assembly version when resolving a Type. Any better ideas?
Fix for handling of closed network streams in VelocityDBServer.