Workaround: Problems editing Visual Studio build definition using 3.0 or 3.0.1 client after editing using 4.0 client

RTC Build Team
Last Updated: June 12, 2012
Build Basis: Rational Team Concert 4.0

Workaround Summary

In V4.0, the underlying representation for a “Jazz Build for Microsoft Visual Studio Solution” build definition has been changed to support multiple invocations of DevEnv.exe or MSBuild.exe. As a result, if you use a V4.0 client to create or edit such a build definition, problems occur when you view or edit the build definition in any release of a V3.0 client, including V3.0.1.

More Information

In V4.0, the underlying representation for a “Jazz Build for Microsoft Visual Studio Solution” definition configuration has been changed to support multiple invocations of DevEnv.exe or MSBuild.exe.

Problem

If you use a V4.0 client to edit a build definition, in any release of a V3.0 client, empty values are shown for fields, such as the solution to build.  If you use any release of a V3.0 client to change the fields, other entries that are usually visible in the V4.0 client might be overridden.

Workaround

Avoid using a V4.0 client to edit “Jazz Build for Microsoft Visual Studio Solution” build definitions until all users upgrade to the V4.0 client. Continue to use a release of a V3.0 client to edit such build definitions until all users upgrade to V4.0.  If you want to use the new support for multiple invocations of DevEnv.exe or MSBuild.exe, you can do so by using the V4.0 client. However, be sure to notify anyone who uses any release of a V3.0 client that they must not attempt to modify the build definitions.

Related Information

Related task:

• 205836: Warn the user if the updated MS build definition is opened in old client(3.x)