Greetings,
Is there a method, short of literally running the alpha5.exe program (and going to Help->About) that you can find out what the patch level is of at least the RunTime programs?
Is there an OFFICIAL A5 distributed file that can be read by a 3rd party program where you can get the patch level (i.e. 3960-3018)?
Is there a way that you can run the alpha5.exe file, with a command-line option to get JUST the program version so that a 3rd party program can querry the runtime installation for that information? (Note: If this were to become a "wish-list" item, I would prefer that a text file be generated in the program folder, such as "a5ver.txt" and/or that an additional command line parameter could be used to give the path/filename where to write the file.)
Lastly, which specific file(s) have the Windows Properties version numbers to determine what the specific release version is of the RunTime?
I do have the ability with the installer I use to put "system dependency checking" into the installer itself... but I need to know the specific files that should be checked.
Any help here would be most appreciated, as this problem refered to in another thread, although very well may have been caused totally by us, is a creditibility issue in my eyes and I want to prevent it from happening again if there is any way possible.
Thanx,
Keith
Is there a method, short of literally running the alpha5.exe program (and going to Help->About) that you can find out what the patch level is of at least the RunTime programs?
Is there an OFFICIAL A5 distributed file that can be read by a 3rd party program where you can get the patch level (i.e. 3960-3018)?
Is there a way that you can run the alpha5.exe file, with a command-line option to get JUST the program version so that a 3rd party program can querry the runtime installation for that information? (Note: If this were to become a "wish-list" item, I would prefer that a text file be generated in the program folder, such as "a5ver.txt" and/or that an additional command line parameter could be used to give the path/filename where to write the file.)
Lastly, which specific file(s) have the Windows Properties version numbers to determine what the specific release version is of the RunTime?
I do have the ability with the installer I use to put "system dependency checking" into the installer itself... but I need to know the specific files that should be checked.
Any help here would be most appreciated, as this problem refered to in another thread, although very well may have been caused totally by us, is a creditibility issue in my eyes and I want to prevent it from happening again if there is any way possible.
Thanx,
Keith
Comment