conflicts when changing project

[Barionics]

Me again!  Another conflict question.

 I am working with two projects, which (for sake of argument) we can call  A and B. 

I work on A for a time. I run my Teststand sequence and it is fine. I then push it to CVS.

Next I switch to working on Project B ( which uses common VIs stored in its own folders). 

However, when I open Project B in LV it is full of Conflicts. These I fix, run the sequence and then save it.

Now I change back to Proj A.  However, it is full of Conflict errors!!!!!!

What is happening!?

 In an effort to fix this, I fully recreated both projects, and explicitly defined which VIs to use in each case and where to get them from. However I still get conflicts when switching.

  Any ideas?

[Sam_Sharp]

You mentioned your TestStand sequence - are you unloading the LabVIEW modules after running it from TestStand (from file->unload modules)? Any LabVIEW code loaded into TestStand will stay in memory until it is unloaded manually (or you exit TestStand).

[billko]

oops ignore this post

[Barionics]

I've even tried rebooting the PC, to be doubly sure of flushing out any VIs in memory.  Also,  I rename the project which I am not working on.

 Out of interest, is it possible to set Teststand to unload automatically, when it finishes running?

[Sam_Sharp]

I believe you can programmatically unload the modules as part of your sequence (e.g. at the end), or add it into one of the built-in sequence models.

If it's still happening after you reboot your PC, then you have a genuine conflict you need to resolve - some VIs are calling VIs from the other project or vice-versa. All of your project specific files should be located in the same folder (or a sub-folder) of your .lvproj file, and anything else (e.g. shared VIs) should go into user.lib/vi.lib etc.

[JÞB]

Now I have a question-  That is not to say the "Load-Unload" files from the *.seq options won't help (They just might)

Does your sequence call vis through the associated lvproj context?  As I understand things, The vi with the right name in the search path options will load first in TS unless, you give it a "Fully Qualified Name" by calling through the *.lvproj at which time the *.lvproj is queried for an exact path.  (Just open a *.lvproj in notepad- you'll understand when you see the vi paths listed in human readable text)

You also seem to have multiple projects (*.lvproj files) linked to common reuse vis.  Where are those common files?  <LabVIEW>\User.lib\MyStuff\ CommonVIsXYZ.lvlib would be a nice parking spot for those  A few more details and we will get you on the path to success! (If my 8-Ball hasn't already given you the right information)