|
I have just identified the problem. We use .vsprops files to specify User Macros, that our vcproj files then reference these .vsprops files and use the macros to build up other values, including OutputDirectory.
I changed one project from using the User Macro to a hard coded value and the incrementing started working...
------- from the vcproj file -------
OutputDirectory="$(IRISOutput)\$(ConfigurationName )"
[*did not* increment version]
changed to
OutputDirectory="c:\common\$(ConfigurationName)"
[*did* increment version]
My question, therefore, is slightly different - Is this a bug and is it something you plan to address? This would be very important to us as several hundred projects in our system use this .vsprops approach.
The vsprops file is specified in the vcproj file, in the <Configuration> tag as such:
InheritedPropertySheets=".\UpperCaseFixProps.vspro ps"
and the vsprops file is a simple XML file which may look something like this:
?xml version="1.0" encoding="Windows-1252"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="TaxLevel1Props"
>
<UserMacro
Name="IRISBase"
Value="c:\release8.7"
/>
<UserMacro
Name="IRISOutput"
Value="$(IRISBase)\common"
/>
<UserMacro
Name="IRISCodeBase"
Value="$(IRISBase)\vss1\IRIS"
/>
<UserMacro
Name="IRISLibs"
Value="$(IRISBase)\Common"
/>
</VisualStudioPropertySheet>
|