This article has been archived. It is offered "as is" and will no longer be updated.
The $(ItemPath) macro incorrectly beautifies the actual path name when a folder name in all caps is included in the path name. For example, if $(ItemPath) refers to the C:\Projects\TEST\Source folder, when $(ItemPath) is resolved it will resolve it as C:\Projects\Test\Source. The difference is that $(ItemPath) changed TEST to Test in the path name.
This can be a problem for some tools or for some platforms or operating systems where path names are case-sensitive. For example, some version control tools that run on UNIX servers may experience a problem if the tools are integrated in the IDE and if they depend on the $(ItemPath) macro.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 23-Sep-2003 12:24 7.10.3266.0 602,624 Vcproject.dll 23-Sep-2003 12:25 7.10.3266.0 1,836,032 Vcprojectengine.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.