What prevents a 32-bit developed vi or project (lvproj) containing many such vis from opening in a side-by-side 64-bit LabVIEW environment?

[*3d0g]

Up till now I have opened the environment, first, and then used the environment to bring in the project or vi.

Is there something written somewhere by National Instruments that guarantees a 32-bit development will never enter a 64-bit environment unless it is specifically requested to do such?  I see a danger of a 32-bit development being accidentally converted to 64-bit via an errant save.  Is the danger unfounded?  Am I just being a worry wart?  Am I free to open a 32-bit vi without fear?

Now you may ask, why should there ever be an errant save?  (I hear 'just be careful about the save button you noob peasant!')  It has been my experience that splats (*) follow projects that haven't been modified simply because "an attribute has changed" -- this being the only explanation given when one can't just exit without being prompted to save or not.  But I didn't change anything!  Too bad.  Choose.  ...technically, there is still Task Manager to abort all NI products to avoid answering the undesired question...

So, am I just paranoid of the side-by-side 64-bit installation?  My apologies if this topic has already been covered, here.  I couldn't find the answer to the question.  

[santo_13]

IMO - You're just paranoid. Even if you accidentally save in a different bitness (though no such nonsense exists), the other bitness can still open the VI.

https://www.ni.com/en/support/documentation/supplemental/18/labview-32-bit-vs--64-bit-applications-f...

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019NyzSAE&l=en-US

[altenbach]

If you configure your Vis to "separate compiled code", the VIs are basically indistinguishable because the platform specific code is stored elsewhere. If not, the compiled code is part of the file and will automatically be recompiled for the new platform and there is nothing you need to do. This is safe.

I assume that 32 and 64 bit LabVIEW are the same version, right?

Things get a bit more complicated if you e.g. call custom DLLs. They are bitness specific. Also all needed drivers need to exist in both environments.

[billko]

I think the VIs are just the source code and it compiles in whatever environment you open it in.  If I'm remembering correctly, it won't even ask you to save when you close it.

[*3d0g]

Correct, both the 32-bit and the 64-bit environments are the same LabVIEW version.

Do you think you answered my question?  I don't think you did.

[santo_13]

1. It is safe to have both 32-bit and 64-bit LabVIEW on the same machine
2. VI contains source code and source code is bitness independent.
3. By default the compiled code is included in the VI, you can change the VI settings to separate compiled code.
4. LabVIEW loads any dependency (VI) into memory when the caller is loaded or a library or project containing it is loaded.
5. LabVIEW does not auto-save the VIs and pop you the question on exit

When you say 'side by side' do you really mean, open the same file in both LV 32-bit and 64-bit at the same time? like two applications opening the same file?

[altenbach]

---

@*3d0g wrote:

Correct, both the 32-bit and the 64-bit environments are the same LabVIEW version.

---

Since this was one of my questions, I assume you are replying to me. Just guessing, because there is no way to tell...

It always helps to quote relevant parts.

---

@*3d0g wrote:

Do you think you answered my question?  I don't think you did.

---

I said "this is safe", potentially answering your main concern. 🙂

[*3d0g]

---

---

Since this was one of my questions, I assume you are replying to me. Just guessing, because there is no way to tell...

It always helps to quote relevant parts.

---

---

I said "this is safe", potentially answering your main concern. 🙂

I don't think this is working correctly.  I'll respond with my next.

[*3d0g]

---

@altenbach wrote:

---

@*3d0g wrote:

Correct, both the 32-bit and the 64-bit environments are the same LabVIEW version.

---

Since this was one of my questions, I assume you are replying to me. Just guessing, because there is no way to tell...

It always helps to quote relevant parts.

---

@*3d0g wrote:

Do you think you answered my question?  I don't think you did.

---

I said "this is safe", potentially answering your main concern. 🙂

---

I didn't mean to quote all the above.  I'll get it eventually.  At least it isn't a huge post.

So, presently I'm seeing in the project that "Separate compiled code from new files" is checked.  If I'm understanding you, what you've said, with this checked at the creation of the project, either the project or any vi in the project is safe from accidently opening in the 64-bit environment LabVIEW.  Correct?

What I have is two icons for LabVIEW in the taskbar at the bottom of the desktop, one is orange and the other is yellow.  The orange shows 32; the yellow shows 64.  Once one of the icons is clicked LabVIEW opens and there is nothing immediately shown to differentiate the environments.  Only through the "about" window does it really become seen what environment was opened.  Unless you know orange from yellow, there is an avenue for error.  One can see the 32 and the 64, but it's still an easy mistake to open one over the other.  To date I've clicked orange with respect to this present project, and then via the opened orange opened my project, after.  For a 64-bit project, substitute yellow and I do the same.

But now what about clicking the project or a file that is in the project, but from outside the project?  If I'm understanding you, it matters not as long as "Separate compiled code" was checked when whatever it is was created.  This is your answer to me.  Or is this not correct for what you're saying?  I would like to find this in the documentation as well, next.

[billko]

I think rolfk once told me that the inability to distinguish which version of LabVIEW you are opening up is a Windows thing, not a LabVIEW thing.  Double-clicking on a file associated with LabVIEW will make it open in the last version of LabVIEW that you used.  More importantly, it will open in the last version of LabVIEW even if you right-click and choose the version you want to open it with.

Unless something has changed, I would advise always to open the the version of LabVIEW you want to use before opening the file.