Can’t save a file setting in a Visual C++ 2013 project

Symptoms
Consider the following scenario:
  • In a Visual C++ project in Visual Studio 2013 Update 2 or later, you use Configuration Manager to create a configuration that's named Release Temp.

    Note Release Temp is forward-matching with another configuration’s name—for example, with a configuration that's named Release.
  • For a .cpp file in the Visual C++ project, you set the Configuration setting to Release Temp.
  • You modify a property value for the .cpp file, and then you save it.

In this scenario, the property value change is applied not only to the Release Temp configuration but also to Release.
Cause
Visual Studio 2013 Update 2 includes some changes in the way that property values are set in a Visual C++ project. The Visual Studio IDE searches for a configuration setting by using a configuration's name and forward-matching functionality.

Because of this change, modified property values for Release Temp are unexpectedly saved in Release, and vice versa.
Workaround
To work around this issue, use one of the following methods:
  • Do not give any configuration a name that might be a partial match with the name of another configuration.
  • Use a version of Visual Studio 2013 that's earlier than Update 2 (such as the RTM version).

This problem is fixed in Visual Studio 2015.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 3097181 - Last Review: 09/30/2015 20:51:00 - Revision: 1.0

  • KB3097181
Feedback