No I don't think there is .. hmm. They may encode this info somewhere in the registry.
Assuming you don't change the Silk versions
all that often. Also assuming that you will be doing this on a machine by machine basis, you may want to create a compiler constant.
Also ASSUMING you actually want to go this route you probably want to make this a string (when I did it I entered 5.0.3 and it tried to interpret it as a number "5.0.3" worked better).
So you can actually just refer to it directly via Silk_Version or some name like that. I realize this is the "Rube Goldberg"
approach .. but I think this is really why people use Silk in the first place!
[This message has been edited by rick_weth (edited 01-04-2001).]
[This message has been edited by rick_weth (edited 01-06-2001).]
You could use Rick Weth's DLL in the downloads section of this bulletin board in Segue section, under heading GetFileVersion.
I use it to determine the versions of EXE's and DLL's used in the product I test. I suppose you could use it to query the version of partner.exe that you use on your given PC's. You could read the version and take whatever appropriate action desired.
[This message has been edited by styler (edited 01-04-2001).]
I am working with some Silk code where the writer modified defaults and browser .inc files. I currently have v126.96.36.199 and v5.0.2 running (bad practice, I know). I was thinking of a way to get the currect .inc files loaded by checking the version at runtime.
Rather than compiler constants, I will design a local .ini file to contain specialized parameters for a machine's test. A setup script can then handle.