With VX1.1, the COM version is different than VX.1, so this can let you know what version the user is running. In my case, I just look to ensure that the environment variable is set so that I know my automation calls will run externally of the program.
Here are two different examples of running through the command window.
Debugging using Visual Studio:
I launch my project through the command window so when I go to debug, the environment variables are set and I know it will create the appropriate objects such as PDB Editor, ect.
It's the same thing for running a script:
Which results in ALE opening:
If I try to run ALE outside the command window, but still configured for VX...I have added this message:
With the MGC Launch feature, it is a batch file that you wrap your executable in. I haven't really used it since I am a developer and not a user, but a user can take my executables, wrap them with the MGC Launch and it works like a batch script. First setting up a temporary environment, then running the program in that environment. The difference is they double click the wrapper and the program "works", where as in the command window you have to browse to the file (or be lazy like myself and drag the executable into the command window).
Hope this helps!