Deployed LabVIEW project has conflicts

[Wim]

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 vi.lib picture.llb)

--> not on a runtime PC (file not found)

 

Did anyone else notice the same behaviour ?

 

Thanks in advance for your help, tips and tricks :-)

 

At first, i thought i had something to do with LabVIEW search paths (because I include vi.lib, it should not search for the vi's in the real vi.lib) but that didn't help... 

http://lavag.org/topic/18620-labview-search-paths/#entry111920

 

[Wim]

Together wit NI we have found the problem.

 

The GDS (Goop development suite) causes the conflicts.

 

The problem is identified, solution is pending.

 

Cheers,

 

Wim