Quote:
Originally Posted by Crossle86
I have been busy with other things for some days now but am back to this problem now. The last reply indicated the 2015 DS does not use the file date as part of its version number...but on my systems this is still happening. The key thing that I am seeing and may explain some of what I have been struggling with is this (which I am looking at on my DS PC right now):
I have two program files:
Driver Station.exe (renamed from DriverStation.exe, believed to be the current vesion)
Driver Station-upd-0.exe (renamed old version)
Now these two programs are both exactly the same size and both programs show the windows properties version of 15.0.0.49156. Yet when I run these programs I get different version numbers displayed:
Driver Station.exe = 05031500
Driver Station-upd-2015-0.exe = 20121300
How is this possible? One thought that keeps recurring is that I have used the wrong installer for the current version, but I followed the links on the current software version web page and installed from there...and version ending in 1500 is identified as the current version...so?
Also note that if the installer is installing a changed program name, Driver Station.exe -> DriverStation.exe, it is not updating the shell registry key that starts the DS program as the Driver users shell to reflect that change. That key still has Driver Station.exe as the alternate shell.
|
I just tested with a recent build of the driver station by "touch"ing the executable and the version reported on the title bar did not change, and neither did the version on the diagnostics tab. Inspecting the code it appears that only the title bar version is the hard-coded version I added. The diagnostics tab uses the Creation Date of the executable, so a touch is not going to change it since that affects the Modification Date. Perhaps what you are attempting changes the Creation Date.
This clearly needs more improvement in the future.