Running the standalone installation of SODE 1.3.4 you can choose the location where SODE will be installed.
Yes, you are right: we are running the installer silently, with only the platform manager showing up. In fact, we'll probably try to skip even that step and have the SODE be configured automatically in future versions of the installer, since many users don't know what to do with the Platform Manager, and assumed the GSX installer is "stuck", because they don't know the Platform Manager is waiting to chose an action and to be closed then.
In any case, since it's installed as part of the GSX installation, it's not as if you can choose the GSX installation folder either...
When I installed GSX some weeks ago version 1.3.0 of SODE was installed where 1.3.4 is the most current version I'm aware of
That's not possible. The GSX installer never included any version older than 1.3.3 and it's not possible that it could have installed 1.3.0, since (as you can see from SODE website), the GSX API was added in 1.3.1. The first time we ever distributed SODE in an installer, was when KMEM was released in June, and 1.3.3 was the version which was current back then.
but you're correct SODE will not downgrade your current version of SODE while running the GSX installation.
Of course it doesn't, that's why the whole issue of containing the most recent version doesn't matter.
However as a customer with lots of 3rd party products it's not easy to keep track of what exact SODE version each 3rd party product was designed for and if you have lots of 3rd party products using SODE you will very likely run into issues.
As a customer of THESE 3rd party products that haven't been updated to support the latest SODE, you sure have every right to complain with THEM, why they still haven't done so. Once you chose to rely on a 3rd party product for development, you should also take the burden to keep up with updates.
In fact, it isn't what you are complaining to us here, about we not including the *very* latest SODE, even when the issue (in our case) is totally safe, since there are no forward compatibility problems from 1.3.4 to 1.4.0, and the installer doesn't "downgrade" it ?
And as already mentioned the compatibility has been much improved lately when it comes to SODE and the products that use it.
Personally though I think SODE so far caused much more issues vs what benefits it has given and I do my best to avoid products that make use of SODE unless there's an airport that I really want to have.
A bit of contradiction here: SODE (as you said), has been improved quite a bit, and it's now quite stable. Do I have to remind you it's a FREE product ? You should expect some issues with the first versions!
It goes back again to the same problem: some developers were too eager to jump on it, and took the risk to include it in commercial product maybe a bit too early, so it's on them now to update their products to support the better versions. We decided to WAIT a bit, and give some feedback too in the process, before adopting it.
I do my best to avoid products that make use of SODE unless there's an airport that I really want to have.
You might have had a point, if you posted this last year, when SODE was in its infancy, but it's not really relevant anymore. Maybe you should say:
"I'll do my best to avoid products that make use of an OLDER version of SODE, which weren't updated by their developers"