Search the Community
Showing results for tags 'conflicts'.
Hello, this is not strictly VI Scripting related but I believe it's a pretty similar topic, so I hope this fits in with the discussion on this board. I am attempting to write a script that parses through the contents of a very large LabVIEW project (thousands of files) recursively and selectively moves/renames some of the files. The basics of this are fairly simple, however I have thus far been unable to come up with a way of moving files on disk that handles all relinking and dependencies without any issues. At a high-level, my question is whether or not the "Move on Disk..." option
Hi Lava, I'm having an issue with a teststand deployment (Teststand 2013, LabVIEW 2013) I have a deployment which deploys my LabVIEW project containing all drivers (classes and lvlibs) for use in my sequences. In the deployment (LabVIEW options), I uncheck "exclude vi.lib", "exclude user.lib" and "exclude instr.lib" because the deployment should also work on an PC that only has runtimes and an operator interface. The build finishes without errors but I cannot open the deployed project... --> not on a development PC because it finds conflicts (XNodeSupport and some vi's in v