Hello,
for custom data types, we do not use the mapping approach (and therefore no NodeSet2 or Types.xsd). We read the data type information from the server, and then provide the custom data types in "dynamic" form (where you e.g. need to access the properties by string names and retrieve them from a dictionary object, and not as named properties of a C# object). The whole thing is described here:
opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2...omplex%20Data%20Extension.html . Example reading code:
opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2...0Complex%20Data%20reading.html .
And it should work. If it doesn't (and gives BadOutOfMemoryException), something is wrong. However, the whole feature is quite complex, so there is little chance of discovering the cause without having a reproducible case that we can debug here, on our side.
Do you perhaps have a demo version of your server that can be run on a PC, or can open a port for us to access it?
(Note: Going to vacation tomorrow - any deep technical investigation need to wait for approx. 2 weeks - apologies).
One last thing: What do you actually mean by "BadOutOfMemoryException"? The name seems to be mangled somehow. Are you talking about
1) .NET exception - which is named OutOfMemoryException (and not BadOutOfMemoryException), OR
2) OPC UA status code/service result - that one is called BadOutOfMemory (i.e. also not BadOutOfMemoryException)
3) something else?
Best regards
