02-11-2010 01:25 PM
@gmart - thanks for that extra info. For the current project I'm working with LabVIEW 8.6.1 Bitter experience over many years (unrelated to LabVIEW I may add) has taught me not to upgrade tools mid project. I do however have LabVIEW 2009, and will move to that for future work, so it's nice to know the feature is there.
Regards,
Bandit
02-11-2010 04:03 PM
Nice, this internl function will be very useful.
02-11-2010 08:43 PM
gmart wrote:
In LabVIEW 2009 (Windows only), you can use the fileVersionInfo.llb located in the labview\vi.lib\Platform directory to retrieve the version information of a stand-alone application or shared library programmatically.
The FileVersionInfo VI in that library uses a bunch of Windows API calls. That seems awfully complicated vs the .NET method. Is there a speed advantage? I would guess there probably is given the poor performance of .NET within LabVIEW, but I haven't tried it with LV 2009.
04-27-2017 03:45 PM
I posted this to another question, but out of all the solutions, I think you'll like this the best:
Try this on for size... I went a little bananas and made a VI that can not only get the build version when the VI is in an executable, it can ALSO extract the build version from a specified project that is currently open when in source mode. It also has decent error reporting too.
Easy to use:
Voila! Update the build version in the project, and it updates in your application no matter how you're running it. I converted to LabVIEW 8.6 so almost anyone can use this.