Open Vi reference for Vis with same names

[abdel2]

Using VI server, is there any way to open reference to a VI on the hard disk even thought a VI with the same name (but different path) is already loaded in memory? I'm trying to see if it's possible without renaming and making sure every single VI I use has a distinct name.

[JK1]

Its not possible to place the vi's with same name in memory i tried doing so but either of the open refnums throwed error saying "not state compatible to run".

But i ran the vi's using call by referance in that case no error but there was racing codition!!!! you may not know which vi will execute and the result might be from any of the vi's

[parthabe]

---

abdel2 wrote: 

 I'm trying to see if it's possible without renaming and making sure every single VI I use has a distinct name.

---

I think we cannot do so even with VI Server.

But, your above statement appears contradictory & confusing to me, in the sense, are you NOT going to rename or are you going to keep a distinct name for each VI?

[abdel2]

Right now I have two Vis with same name but different paths which is the reason why Vi server is opening reference to the wrong Vi. To fix it, I would have to rename one of them.

My goal is to create source distributions (SDs) for "modules" that can be implemented in my application over time. I can then run whatever Vis I want from the SD at runtime. Obviously, every single SD has to have Vis that have distinct names not just relative to the main application Vis but also Vis of other SDs that might be running in parallel. For now, I can give different names but as the # of modules increases, it will be hard to have some Vis that don't have the same name. Only other way I can think of to fix this is by creating an executable out of each SD and running it separately from the main application.

[parthabe]

---

abdel2 wrote:

For now, I can give different names but as the # of modules increases, it will be hard to have some Vis that don't have the same name.

---

It wont be tough to keep distinct names.

Just prefix or suffix your module name to the original VI name, so that you SDs will have VIs with same/similar functionality, but never conflict with each other when called during run-time. This is the procedure we follow in our project currently. We have gone ahead with the extent of packing all the DUT SDs (LLBs) into one complete auto-installer, so that in the target PC, everything get unbundled & installed into the appropriate folders that we have added while creating the installer.

[Darren]

An alternative to prefixing the names of the VIs would be to use project libraries.  If every module were in a separate project library, they would all be namespaced to those libraries, and you wouldn't have any name collision issues.  Note that project libraries are available in LabVIEW 8.0 and later.

[parthabe]

Do you mean the LVLIB, Darren?

[Darren]

Yes, Project Libraries are .lvlib files.  See the LabVIEW Help on Project Libraries for more info.