Visual Studio and .NET Framework Home
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
as Won't Fix
3/12/2008 2:38:42 AM
User(s) can reproduce this bug
Found using DSL Tools, but probably a more generic problem.
When regional options set to Turkish, the following vsct file
... more ...
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.
Visual Studio 2008 (All Products and Editions)
Windows Server 2003
Operating System Language
Steps to Reproduce
- Change regional options to Turkish
- Create a new Domain Specific Language Designer project, accepting the defaults.
- Build the project.
Compile time errors for each <Extern> statement in vsct file, and some other errors due to the lack of data in the include files.
No compile time errors.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
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.
Wes - Visual Studio Platform
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.
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
© 2013 Microsoft