SDK: VSCT compiler incorrectly changes the case of the path of additional include files when the regional options set to Turkish, resulting in compile time errors - by Gokhan Altinoren

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 332672 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/12/2008 2:38:42 AM
Duplicates 332675 Access Restriction Public

Description

Found using DSL Tools, but probably a more generic problem.

When regional options set to Turkish, the following vsct file

<CommandTable ...>
  <Extern href="stdidcmd.h"/>
  ... more ...
</CommandTable>

results in a compile time error:

"File not found: Unable to locate 'stdidcmd.h' on the include paths provided"

The problem is, VS build process tries to resolve the additional include using the following path:

C:\PROGRAM FİLES\MİCROSOFT VİSUAL STUDİO 2008 SDK\VİSUALSTUDİOINTEGRATİON\COMMON\INC\stdidcmd.h

It appears that the uppercase conversion of the path does not use invariant culture. "i" is represented as "İ" in uppercase form in Turkish, not "I" as in English.

Microsoft.VsSDK.targets prepares the path in lowercase, so I'm guessing that the problem is somewhere around Microsoft.VisualStudio.CommandTable.VSCTCompiler in VSCT.exe . The issue is OS independent and can also be reproduced under Vista.
Sign in to post a comment.
Posted by Microsoft on 4/24/2009 at 2:07 PM
Thank you for your feedback. Unfortunately, given our current schedule, we will be unable to address this issue for this Visual Studio 2010. We will be actively tracking this issue for the next release of Visual Studio.

Thanks,
Wes - Visual Studio Platform
Posted by Microsoft on 3/12/2008 at 10:18 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team