LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Automatically Including Build Date

We have some LabVIEW code that is built into an .exe/installer and it has an indicator that shows the date it was built and the revision number for that build. Currently, we have to manually set the date and revision number each time we build the program. I don't think the way we do our revision scheme can be automated with LabVIEW during the build of the installer or .exe file. However, it seems like there should be a way to incorporate the build date into my code from the build process. Is there such a thing? If not, does anyone have any suggestions for automatically including a build date into the LabVIEW code so that I do not have to remember to do this manually each time?

 

Thanks in advance.

Message 1 of 6
(4,555 Views)
The date that the application was build, is it's last modified date!

So, use File/Directory Info, and wire the path to the application to it. The
returned time stamp should be the build date of the executable.

I'm not sure if this is "safe" enough for you. It could be that the last
modified date changed by moving it aournd networks or such actions, but it's
so simple, it sure is worth a try!

Regards,

Wiebe.


Message 2 of 6
(4,534 Views)

I would love to see some dynamic entries into the builds, but currently, it's not available.  (I would like to see in the version information major.minor.fix.sourcecodecontrolrevision)

 

I would go with the created date, instead of the last modified.  people could change the extension, then change it back and fudge the modified date.

0 Kudos
Message 3 of 6
(4,527 Views)

I can't remember where I found these, so I cannot give due credit, but these VIs will give file info. If you point these to your exe file then you can get the file version etc.

 

EDIT: If you leave the path blank, then it follows the call chain to the app. In development this will point to LabVIEW, but in a compiled exe it will be your app.

Message Edited by yenknip on 02-03-2009 01:07 PM
_____________________________
- Cheers, Ed
0 Kudos
Message 4 of 6
(4,523 Views)
There are some OpenG VIs that allow you to build the application programatically.
Message Edited by ceties on 02-03-2009 08:56 AM
LV 2011, Win7
0 Kudos
Message 5 of 6
(4,502 Views)

"Britoa" <x@no.email> wrote in message
news:1233666605189-845956@exchange.ni.com...
> I would love to see some dynamic entries into the builds, but currently,
it's not available.&nbsp; (I would like to see in the version information
major.minor.fix.sourcecodecontrolrevision)&nbsp;I would go with the created
date, instead of the last modified.&nbsp; people could change the extension,
then change it back and fudge the modified date.

First, if you copy the exe, the creation date changes! This is even easier
then renaming, and this will probably be done many times by the developers

Second, renaming the exe does not change the date modified!

There are ways to change the date modified, and it is indeed very easy. But,
whatever way you think of, it will be easy to change it, unless you are
going to hash it, or encrypt it.

Regards,

Wiebe.


Message 6 of 6
(4,472 Views)