Network Variables using UDP on target machine

[sparkymark567]

I have a quite serious problem, where my measurement studio application runs fine on a development PC, but on the target machine it falls over. I believe I have found the cause of the problem, but I don't know how to fix it.

When I run the application on the development PC, I can monitor the network traffic using "Microsoft Network Monitor". I can see that my network shared variable data (variables, hosted by CRIO)  is contained in TCP/IP packets (as it should be). But when the application is deployed on a non development PC, the shared variable data appears exclusively in UDP packets.

It seems to me that the merge modules (automatically picked up by the installer) somehow contain software components that are different from that running on the development PC.

Any suggestions would be gratetfully received.

I have tried my local NI support team already, but I'm not getting very far with them at the moment.

Thanks.

[sparkymark567]

NI have now raised a CAR (i.e. bug report) for this problem. As a work round, they suggest installing LabVIEW runtime on the target machine. This could be included as part of the Visual Studio installer project(?) It is obviously not a very good solution, but it is probably workable.

I noticed there are a lot of people here with install problems, how do you include the NI dependencies in your projects?

We add the primary output of the project, so that the required merge modules are picked up automatically. But, the installer generates 15 warnings, which all state "2 or more objects have the same target location". Does everybody else get these warnings? is the way to get rid of them?