The JADE 2022 release meets tomorrow’s business demands.
With the JADECare deployment methodology having to cater for features which start in a specific hot fix and the hot fix being released in the system files (.bin) it is an urgent requirement that we are able to programatically access the version information for a set of system files. This will allow us to identify whether a hotfix is in-place or not.
We can easily identify a hotfix where an exe or dll is part of the hotfix by using the product version property but this is not available for JADE's system files.
This was earlier requested in NFS 52755 but we have user-cases now that require this ability (ie hot fix 18.0.01.049)
Martin Jagers
Am I correct in assuming that when bin files are released in a hot fix, they are always released as a full set?
Yes, we could parse the versioninfo.txt but what a painful way of doing this.
And the feature I'm looking for is to be able to look at this file externally when it is not a part of my set of database files.
Examples:
So please review this JEDI from the point of view of looking at the bin files as external files. In the second example we could run an application that returns the required information but that doesn't satisfy the first example and why the DbFile::getPatchVersion is not appropriate.
You know you could always have done this by parsing a versioninfo.txt. Also, only bother doing getPatchVersion for _system: the others will always be the same as _system.
Just noted that there is a method on DbFile class called 'getPatchVersion'. So by checking all files with kind of System (DbFile.Kind_System) we can get this information already.
Please close this JEDI.