Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to Get Build Date & Version Info from a Exe ??
Message
From
28/10/1999 07:49:52
 
 
To
28/10/1999 07:36:39
Vinod Parwani
United Creations L.L.C.
Ad-Dulayl, Jordan
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00282845
Message ID:
00282902
Views:
20
>>>>>>>How to Get Build Date & Version Info from a vfp generated Exe ??
>>>>>>
>>>>>>In VFP6, you can use AGETFILEVERSION(); prior to that, you needed to use a FoxTools function - check George tasker's Extended FoxTools Help from the Files Section on UT for details on how the FoxTools function works.
>>>>>>
>>>>>>SYS(16,0) will get the name of the executable file that started VFP; this won't be very helpful if you use a Launcher app, since the launcher is the actual executable being run.
>>>>>
>>>>>Thnks for the reply.. Pls note foxtools function GetFileVersion is returning version info.. but not the Build Date..
>>>>>
>>>>>Can u pls tell me how to get "Build Date"
>>>>
>>>>I don't know the FoxTools stuff, which is why I referred you to George's docs; the build date isn't carried in the header except as comments AFAIK - the version should identify the build. Sorry if this doesn't help. It is not a standard item in the resource header, but can be carried in a comments string block in the header. The MSDN docs for Visual C++ discuss the resource editor information in detail in the Adding User Interface Features topic's FAQ - I do not have a URL for this.
>>>>
>>>>My own approach to this is to have the Build number be unique and to increment the revision per compilation, the minor build per release, and major build when distinct versioning of the application occurs, such as when major new functionality is added or language versions or major design changes occur.
>>>>
>>>>The standard editable blocks carried in the .EXE resource are:
>>>>
>>>>Comments, Company Name, File Description, Copyright, Trademark, Product Name, Language ID
>>>>
>>>>Additional details such as internal names, original file names, and whether the executable is self registerable are also available. The VFP6 docs for AGETFILEVERSION() list all the major information in the resource header.
>>>>
>>>>The Creation date is carried as a part of the directory entry, not part of the version information header.
>>>
>>>Thnks for the detailed reply...
>>>
>>>I was trying to show build date in abt. box of my application, so i can verify that latest version is installed on user's computer..
>>>
>>>I'll try to use version no. instead..
>>>
>>>Thnks for the help..
>>
>>You might want to look at the information carried in the Help/About screens of commercial products; even MS's own stuff carries build detail and not the date/time for the compile (look at Help/About for things like IE5, or VFP, or even Microsoft's own Help Control and you'll see this.)
>
>Pls note in vfp 5.0a, it is showing
>
>Version Date : October 21, 1997
>Resource file : ........
>Product Id etc..
>
>Same way i was thinking to display
>
>Last Updated On : [Build Date here]

Go top Windows Explorer, rigth click the executable, pick properties, and look at the Version tab.

Then look at the details for the file, and you'll find that the date shown in the Help/About box matches the date stamp on the .EXE file directory entry - in my case, for VFP5 it's 10/21/1997. This you can get back with ADIR() - the third column is date last modified. With NTFS, the creation date is stored separately and can be retrieved via API calls, but it's still part of the directory entry not the resource header.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform