[CONNECT] Determine MicroStation version in Configuration File

Is it possible to determine the version of MicroStation using configuration file processing?

In particular, I need to distinguish between CONNECT 10.04 and CONNECT 10.05.  That is, I need both the major and the minor version numbers.

  • Hi Jon,
    Don't know, I will enquire.

    Why do you need to do this?

    Regards

    Marc

  • what is the need for determining the version ? is there a reason an older version is being used ?

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • Unknown said:
    What is the need for determining the version ?

    Unknown said:
    Why do you need to do this?

    Bentley Systems developed MicroStation CONNECT originally using the compiler and linker supplied by MicroSoft Visual Studio 2012.  MicroStation C++ applications developed using that same version of Viz Studio are binary compatible with MicroStation CONNECT up to v10.04.

    From CONNECT v10.05 Bentley Systems are using Viz Studio 2015.  Consequently, Independent Software Developers (ISDs) must also use that version of Viz Studio.  However, the compiler lays out binary data differently between the two versions.  A MicroStation app. developed using Viz Studio 2013 will work with CONNECT versions up to 10.04 but not with 10.05 and later; equally an app. developed using Viz Studio 2015 will work with CONNECT 10.05 and later but not with 10.04 or earlier.

    Customer may have multiple versions of MicroStation CONNECT installed.  An ISD may need to deliver two versions of the same app., functionally identical but built using two versions of Viz Studio.  Since the app. name of those two version will be the same, the only way for customer to distinguish them is to deliver the app. to a named folder, not to MS_MDLAPPS. At the time MicroStation starts, the configuration must determine whether that instace is 10.04 or 10.5 to be able to load the correct binary when user does MDL LOAD APPNAME.  That's why I want to implement some configuration logic to point MS_MDLAPPS_10_X at the folder appropriate to the minor version of MicroStation.

     
    Regards, Jon Summers
    LA Solutions

  • Customer may have multiple versions of MicroStation CONNECT installed. - How would they be doing this ?

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • Unknown said:
    How would they be doing this?

    Because that's what customers do: what you least expect them to do.

    Sensible customer A decides to upgrade to MicroStation CONNECT v10.05.  Their IT group is on the ball and updates each and every computer on their network with the new version.  No problem!  ISD ships them the v10.05 version of their app., which works on all computers.

    Less organised customer B decides to upgrade project group B.1 to v10.05 but leaves groups B.2 and B.3 on v10.04 or earlier.  ISD has to ship versions 10.04 and 10.05 of his app.  Customer B has to figure out that group B.1 gets the latest version 10.05 of the app. and group B.2 gets the earlier version.  Group B.3 has a mix of 10.04 and 10.05 versions.  Now you have a logistical nightmare!

    Having a configuration that sorts this mess out automatically is the obvious solution.  However, what's not obvious is how to implement the configuration logic.

     
    Regards, Jon Summers
    LA Solutions