Any way to mass compile to previous version?

[kevmi2ca]

I have 7.1.1 and want to mass compile a directory to 7.1.

Thanks.

[PJS]

If I am not mistaken, you can open 7.1.1 files in version 7.1, but not 7.0.  That being the case, just open it in 7.1 and mass compile from there. Otherwise, your options become more limited.

[JICHFI]

You can use this Invoke Node to Mass Compile to older version.

[altenbach]

---

JICHFI wrote:

You can use this Invoke Node to Mass Compile to older version.

---

Saving for a previous version has nothing to do with a masscompile.

---

kevmi2ca wrote:

I have 7.1.1 and want to mass compile a directory to 7.1.

---

Even more importantly, 7.1 is not a previous version of 7.1.1. The two are fully compatible with each other, with 7.1.1 having a few minor bug fixes.

Your question makes little sense. Can you explain a bit more what you are trying to achieve? What problem are you trying to solve?

[JICHFI]

From LabVIEW help

Mass Compiling VIs

«When you open a VI last saved in a previous version of LabVIEW, LabVIEW automatically converts and compiles the VI. You must save the VI in the current version of LabVIEW or the conversion process, which uses extra memory resources, occurs every time you access the VI.»

So if you have VIs in a newer version of your LabVIEW version, you need to save them all with that version to your version. So I don't know who you are but I think that Save for Previous version does something with mass compile, this above VI opens recursively a bunch of VIs and save all of them to the desired version with the same filename.

Message Edited by JICHFI on 08-23-2009 03:45 AM

[altenbach]

---

JICHFI wrote:
«When you open a VI last saved in a previous version of LabVIEW, LabVIEW automatically converts and compiles the VI. You must save the VI in the current version of LabVIEW or the conversion process, which uses extra memory resources, occurs every time you access the VI.»

---

Read your quote and the question again. Your quoted section talks about what happens if you open a VI that has been saved in a previous version in the current version, i.e. open a lower version in a higher version.

This discussion talks about going from a higher version to a lower version. This is 180 degrees different.

The quote is not relevant to this discussion!

---

JICHFI wrote:

So I don't know who you are but I think that ...

---

I don't know who you are either except what is visible in your profile... 😉 It should not be relevant wo I am.

---

JICHFI wrote:

Save for Previous version does something with mass compile, this above VI opens recursively a bunch of VIs and save all of them to the desired version with the same filename.

---

Save for previous has nothing to do with masscompiling!

• Masscompiling takes an existing folder full of VIs and converts them to the current version, overwriting the old versions in the process.
• Save for previous creates a new folder containing new copies of all relevant VIs downconverted to the target version. Often, especially in order versions, the downconverted VIs need to be compiled again the first time they are opened in the old version (you would see something like "VI converted from 7.1 to 7.1"). They are NOT masscompiled. To fix this, you could use the previous version to masscompile the downconverted folder, or you could just do a "save all" the first time after opening in the old version. This has nothing to do with the question.

All this discussion is irrelevant because it is NOT possible to save as 7.1 from 7.1.1. They are fully compatible.

Since the original question does not make sense, we need further information from the OP.

[JICHFI]

And the subject title is "any way to mass compile to previous version?"

So you, analyze that question, and give us the answer to that question, he asked it 2 years ago so I just replied to the subject title, not for 7.1.1 to 7.1 which I knew is the same file format... I guess that guy doesnt need an answer today, I posted it for people who will wonder how to save a full project to a previous version, which I think is the better way...

But the above VI is usefull for a "kinda" mass compile to previous version.  Ok we understood that it's not a real "mass compile" at all but at least that's the way I was thinking we can name this idea. You can reply that you disagree with the 7.1.1 to 7.1 but I think that after 2 years he understood it...

This "fake" Mass compile to previous version is better than NI "Save for previous" because they require to save it in another location which might be annoying sometimes.

So, come on...

[smercurio_fc]

---

JICHFI wrote:

This "fake" Mass compile to previous version is better than NI "Save for previous" because they require to save it in another location which might be annoying sometimes.

---

Actually, the NI version is better because it doesn't overwrite your code, which is the actual part that's annoying. 

[altenbach]

---

JICHFI wrote:

So, come on...

---

Sorry, I still don't know what kind of point you are trying to make. 😉

You should NEVER downconvert by overwiriting existing files, that's just asking for trouble. Sometimes there are features that are not available in an older version and you end up with a broken VI. Not everybody has excellent SCC as you apparently do, so this code could spell disaster when blindly used by a reader here. This code is dangerous.

This thread is about 7.1 and similar. I am pretty sure the recursive file list was not available in 7.1 (?). You talk about projects, which did not exist back in 7.1. Besides the LabVIEW project has an option to save an entire project to a previous version.

If you think you have a hot new idea to solve a perceived problem, you could post it as a new example over in the LabVIEW community, instead of tacking it at the end of an somwhat unrealeted ancient thread. This would also give you more space to rationalize what you are trying to do, describe the code in detail, discuss possible problems and warnings, and attach some sample code. At the same time, you should also cleanup your code a bit. For example it might be a good idea to close all the many reference you open. Good luck! 😄

[JICHFI]

I understand that NI did not put it in the software to prevent data loss as you mean. That's why i was not willing to propose it as a new feature in software, come on!

But if the developper knows what he is doing, I think that idea might be okay in some cases, but of course, it's not safe to use it if you don't have backups.

But for example, usually I use a lower version in my labs, so almost the whole code comes from that lower version, And I use the newest version at home, so if I work a little bit from home and don't want to lose my original paths and lose time to rename the paths, delete the original... So that code might be alright if we close our references, yeah it's not a full program as you can see, it shows the basic idea.

Come on guys ;o)