Leaderboard

The easiest and safest way is to use a static VI reference - you drop it from the app control palette and then drag your VI into it. You can then use the name or path property from that. It will work correctly both in LV and the EXE and will also force the VI into the build. P.S. In the image the reference is connected to the type input because I often configure it to be strictly typed and then you can use it with the ACBR node.

FYI: I've just posted on the Idea Exchange about improving IDE performance when working with classes. Would be nice to get some more visibility on these issues! http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Improve-IDE-performance-when-working-with-lots-of-classes/idi-p/2150332

I think you've misunderstood something slightly. Accepting multiple connections on a single port is the same regardless of whether the connections originate from a single IP address or different addresses. Outgoing connections are assigned ports (usually automatically), and so long as the port/IP address combination is unique, there should be no problem. To accept multiple connections you need to understand the difference between a listener and a connection. In newer versions of LabVIEW (2011, haven't checked 2010), TCP Listen has a listener output. In older versions (LabVIEW 2009, maybe 2010) you need to use TCP Create Listener and Wait on Listener yourself. When Wait on Listener returns a new connection, you need to handle that new connection and continue listening on the listener for more connections. There are a couple of ways to handle this; the common ones I know of are 1) dynamically launch a VI to handle the new connection, or 2) add the new connection to an array of connections in a separate loop, and iterate through the connections continuously, sending or receiving data as appropriate on each one. You may find this thread about listeners and connections helpful. It also explains why you should not open and close the listener for every connection, in case you're doing that. http://forums.ni.com/t5/LabVIEW/TCP-IP-feature-or-bug/td-p/832692