What is your SmartComponent Library version?

What is your SmartComponent Library version?

Every release of the SmartComponent Library carries information that identifies exactly which version is installed on a customer's project. Knowing this version is essential when you log support calls, reproduce issues, plan an upgrade, or verify that all developers and build environments are working against the same framework build. The primary source of this information is the include file Consultingwerk\frameworkversion.i, which is part of every SmartComponent Library release.

The frameworkversion.i file

The include file Consultingwerk\frameworkversion.i is automatically generated as part of Consultingwerk's release process. It contains the release name, the release number (the Perforce change list number at Consultingwerk) and the release date in a single line, for example:

Release 11.3 #31102@2014-06-26

The components of this string are:

Part

Example

Meaning

Part

Example

Meaning

Release name

Release 11.3

The name of the SmartComponent Library release.

Release number

#31102

The Perforce change list number at Consultingwerk that identifies the exact build.

Release date

2014-06-26

The date the release was built.

You can simply open Consultingwerk\frameworkversion.i in any text editor to review the release number — no compilation or running code is required.

Reading the version from within your application

If you need access to the framework release number at runtime, create an instance of the class Consultingwerk.FrameworkVersion and read the return value of the GetVersionString() method:

MESSAGE (NEW Consultingwerk.FrameworkVersion()):GetVersionString() .

The class Consultingwerk\FrameworkVersion.cls is shipped alongside frameworkversion.i in every build and returns the same version string shown in the include file.

When do you need this information?

Provide the version string from frameworkversion.i whenever you:

  • log a support call with Consultingwerk, so we can match your build to the corresponding source and release notes;

  • reproduce or report an issue, to ensure the behaviour is being analysed against the correct framework build;

  • plan or verify a framework version update on a customer project;

  • confirm that all developers and build/CI environments share the same SmartComponent Library version.