If a scriptclass object is returned from a job created by start-job, any members using strict-val will now be converted to noteproperty from scriptproperty and will no longer support type enforcement.
Workaround is to not use strict-val for classes whose objects must be deserialized.
Additionally, method invocation via . will not work on such objects -- anything that is not a noteproperty gets removed or converted to noteproperty on deserialization.
Workaround is to use |=> to call methods rather than ., as the former dynamically restores methods when invoked.
If a scriptclass object is returned from a job created by
start-job, any members usingstrict-valwill now be converted tonotepropertyfromscriptpropertyand will no longer support type enforcement.Workaround is to not use
strict-valfor classes whose objects must be deserialized.Additionally, method invocation via
.will not work on such objects -- anything that is not anotepropertygets removed or converted tonotepropertyon deserialization.Workaround is to use
|=>to call methods rather than., as the former dynamically restores methods when invoked.