Does LVCompare require different file names?

[Bob_Schor]

I've got about 1000 VIs that I want to check to see if they are different.  If I try comparing them within LabVIEW, I need to rename one of the files since the Compare tool only works with VIs in memory, and they need to have different names (I typically add "x" to the name of one of them).  Clearly not a good solution for 1000 files!

So I thought about using LVCompare.  I'm especially intrigued by the ability to ignore "cosmetic changes" (which is why I don't simply use a "Binary Compare" utility).  The discussions and (sparse) descriptions of it made it seem to allow files of the same name, as long as they had different paths.  However, when I did a trial, I got the "Need different names" error message.

Is there a way to do this?  [If necessary, I could always copy one file to a temp folder, rename it by appending "x", then call LVCompare, but this is certainly not "elegant" ...].

Bob Schor

[smercurio_fc]

You can put the VIs into different projects. The projects provide the namespace distinction that you need, allowing the VIs to have the same name.

[Bob_Schor]

---

@smercurio_fc wrote:

You can put the VIs into different projects. The projects provide the namespace distinction that you need, allowing the VIs to have the same name.

---

I'd read the same thing, but don't understand what it means.  The instructions for LVCompare suggest the syntax is something like "LVCompare <File 1> <File 2> <options>".  How does one go about putting an older version in a "different project"?  I tried opening the older version's project and renaming the project "Older Project", but when I specified the files as "NewVersionFolder\Test.vi" and "OlderVersionFolder\Test.vi", I got "Error 193" (undefined).  Even though the project's name is different, the file name remains the same (though the path is different).

Forging ahead ...

BS

[smercurio_fc]

moved