Interesting problem. I just tried to use VI Server, but I get Error 15, resource not found for most VIs in the exe. It looks like only VIs that had their front panel built into the executable retained their version info. You can, however, get a list of all VIs in the executable which is better than nothing.
Also, you don't need to change the name. I left the file as .exe and LV listed the VIs just fine. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Joerg Hessdoerfer > Sent: Thursday, June 03, 2004 11:58 AM > To: Info LabVIEW (E-mail) > Subject: Re: Detective work on built executables > > > Hi, > > On Thursday 03 June 2004 17:43, Will Keogh wrote: > > Dear built-executable gurus, > > I have an ugly labview problem. I have inherited a suite of labview > > programs, consisting of built executables that are known to > work, and a > > vast, disorganised pile of vis. The challenge is to > reconstruct working > > versions of the source code corresponding to each > executable. What makes it > > hard is that there are 1/2 doz different versions of each vi, and no > > obvious way to tell which are the 'good' ones. I am hoping > that it may be > > possible to dig into the exes and find out what vis went in > to them (I > > understand that I certainly can't get the original source > code out of the > > exes, but any clues would be helpful). Does anyone have any ideas? > [...] > > Well, you can certainly try to rename the exe to .llb, then > you can browse it > with LabVIEW functions (List directory...). You could then > try to open a ref > to these VIs, and try to figure out the VI rev via property > nodes (I really > don't know if this is in the built app, though). > > Hope this helps, > Joerg > -- > Leading SW developer - S.E.A GmbH > Mail: [EMAIL PROTECTED] > WWW: http://www.sea-gmbh.com >
