_USE_RTM_VERSION 

This topic is new for Visual Studio 2005 SP1.

Define the macro _USE_RTM_VERSION if you want to ship an application that was rebuilt by using Visual C++ 2005 Service Pack 1 without redeploying any Visual C++ redistributables. For recommendations on how to deploy updates to your application that was built by using Visual C++ 2005 Service Pack 1, see Redeploying an Application Containing a Visual C++ Service Pack or Hotfix.

In general, do not define this macro unless:

  • You are building a component that will be used together with an application that already deploys the Visual C++ 2005 redistributables and the component does not install any redistributables. If possible, update the application at the same time that you release the new component, thereby eliminating the need to define _USE_RTM_VERSION.

  • You are building a patch for an application and do not update the Visual C++ assemblies. However, it is better to redeploy the new Visual C++ assemblies with the patch and avoid using _USE_RTM_VERSION.

The following tables describe which manifest is used by your application in various situations:

C Runtime Library

Is _USE_RTM_VERSION defined? Is header included? Compiled with /Zl? Version in manifest

No

No

No

Visual C++ 2005 Service Pack 1

No

No

Yes

Visual C++ 2005 Service Pack 1

No

Yes

No

Visual C++ 2005 Service Pack 1

No

Yes

Yes

Visual C++ 2005 Service Pack 1

Yes

No

No

Visual C++ 2005 Service Pack 1

Yes

No

Yes

Visual C++ 2005 Service Pack 1

Yes

Yes

No

Visual C++ 2005

Yes

Yes

Yes

Visual C++ 2005

MFC and ATL

Is _USE_RTM_VERSION defined? Compiled with /Zl? Version in manifest

No

No

Visual C++ 2005 Service Pack 1

No

Yes

Visual C++ 2005 Service Pack 1

Yes

No

Visual C++ 2005

Yes

Yes

Visual C++ 2005

OpenMP

Is _USE_RTM_VERSION defined? Version in manifest

No

Visual C++ 2005 Service Pack 1

Yes

Visual C++ 2005

See Also

Concepts

Redeploying an Application Containing a Visual C++ Service Pack or Hotfix