Mismatching VeriStand .NET API versions between testing tools and the client custom device result in intractable errors

[rtzoeller]

If a custom device tries to use the testing tools with a different version of the VeriStand .NET API specified, specific calls (such as getting the BaseNodeType) will fail with surprising error messages (1058, 1172, etc.). It is not clear how to fix it from the errors. We could likely detect this problem and show a better error message in this case, or possibly (?) fix it at runtime.

This can be worked around by using config files to pin both the testing tools and the custom device to the desired year-version of the .NET APIs.

[rtzoeller]

FYI @buckd

[AndreasStark]

@rtzoeller
I just ran into that issue :( I tried to override IP address.

[Overrides]
"Targets/Controller/IP Address" = "NI-PXIe-8840-2F27418F"

How can I resolve that on my local machine (using 2017)?

[tannerblair]

Alright, this one got me. @rtzoeller or @buckd, can you not get the BaseNodeType any more?

[rtzoeller]

@tannerblair you can; nothing's changed in the underlying APIs. BaseNodeType still underpins all of VeriStand's (de)serialization and data storage.

As described in the original issue, usually errors in this area are from trying to use assemblies from different versions of VeriStand concurrently.