SHowell73 wrote:I have multiple versions of LabVIEW on my development PC at work, as we have clients with different versions, which is I am sure the normal thing. Alot of the other developers at my office are using virtual machines and have a different version of LabVIEW on each virtual machine. I am not that savvy with virtual machines, so I havent done it as of yet. I seem to remember a CLA telling me one time something about values of a certain datatype are not transported correctly when using a virtual machine? I think it was something he had to change to a string to get the value to go to an RT target, I cant really remember as it was over a year ago.
Anywho, I sometimes have issues with multiple versions on my machine, as it always seems to launch the last version I had running when I launch from the vi itself in the folder structure instead of opening LabVIEW and opening the project in the correct version. GAH!
Steven, The main issue here is multiple app instances of LabVIEW (The same exe!) on the same machine. The problem is do I have xyz.vi in context and what about the ini updates? Again, it is frightening enough that few Champions dare tread the path. Launching multiple versions of LabVIEW (In WIN OS's) follows a simple rule. the vi opened from the windows explorer will open in the last version of LabVIEW to have opened a vi. But, you should be using projects anyway! and opening projects from the recient list or the GSW is safe.