Custom Device XML Editor Feedback

[MichaelAivaliotis]

I wanted to use this tool so I installed the VIPC posted here:

https://forums.ni.com/t5/NI-VeriStand-Add-Ons-Documents/VeriStand-Development-Tools-VIPC/ta-p/363268...

It turns out that the VIPC is missing an important dependency. The XML editor uses the Configuration Editor Framework which is not included in the VIPC, so I suggest that be included. However it really should be a dependency of the XML editor.

Regardless of this obvious omission, and even after I install that dependency, the tool still doesn't run because of the following missing component:

NationalInstruments.Veristand.XMLReader.dll

No clue what this is or where to find it. Any ideas?

I tried posting this bug on Github, but that repo seems to be empty:

https://github.com/NIVeriStandAdd-Ons/Custom-Device-XML-Editor

[Kreative24hk]

Hi, Michael.

I also had a same problem with you. Is there anyone who can help us?

[Stephan_D]

HI guys,

I found this asembly in this folder:

C:\Windows\Microsoft.NET\assembly\GAC_MSIL\NationalInstruments.VeriStand.XMLReader\v4.0_7.0.0.0__a6d690c380daa308

I got rid of the broken run error after I pointed labVIew to the file located in this folder.

Stephan

[JohannS]

Each (year) version of VeriStand installs a unique version of the .NET assemblies to the GAC. For example on a system with VeriStand 2016 - 2019, I have the following XML Reader assemblies in my GAC.

VeriStand VIs referencing .NET assemblies are strictly versioned: If you save VIs referencing a particular version, then it will be broken if you open it on another machine without the matching assembly version. The VeriStand Custom Device Build Tools handle this by generating .NET configuration file in the project folder. The .NET configuration file redirects the dependencies to use the specified version in your GAC.

1. Copy VeriStand .NET configuration file to your project folder
2. Rename .NET configuration file to match your project file, e.g. Untitled.lvproj.config for Untitled.lvproj.
3. Update newVersion elements to reference desired assembly version, e.g. newVersion="7.0.0.0".
4. Open project (without errors)

For more information, read https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019NYrSAM&l=en-US