Microsoft KB Archive/315472

= Error message when you use &quot;Start Without Debugging&quot; mode: &quot;The filename, directory name, or volume label syntax is incorrect&quot; =

Article ID: 315472

Article Last Modified on 1/26/2006

-

APPLIES TO


 * Microsoft Visual Basic .NET 2002 Standard Edition
 * Microsoft Visual C# .NET 2002 Standard Edition
 * Microsoft Visual J# .NET 2003 Standard Edition

-



This article was previously published under Q315472



SYMPTOMS
When you start your project in the Visual Studio .NET development environment in Start Without Debugging mode, the project may fail to run, and then it returns an error message similar to the following:

Error while trying to run project: Unable to start debugging.

Unable to start program 'C:\Documents and Settings\currentuser\My Documents\Visual Studio Projects\???\bin\Debug\???.exe'.

The filename, directory name, or volume label syntax is incorrect.

The question marks in this error message may appear as boxes or questions marks, depending on whether the code page for the language used in the project name is installed. If the code page is installed, the question marks appear as actual characters.



CAUSE
This behavior occurs when the project name contains characters that do not match the user locale and user interface (UI) language settings of your computer's operating system. For example, this behavior occurs if the project name contains characters from the Russian code page, and the user locale and UI language settings are set to English.

If you install the code page for the given character set, this may affect the information displayed in the error message, but it does not resolve the underlying problem.



RESOLUTION
To resolve this problem, make sure that the user locale and the UI language settings are the same, and that they match the locale of the characters that compose the project name.

To set the user locale on a Microsoft Windows 2000-based computer, follow these steps:
 * 1) Click Start, point to Settings, click Control Panel, and then double-click Regional Options.
 * 2) Click the General tab, and then under Settings for the current user, select the locale that you want in the Your locale (location) list.

To set the UI language on a Windows 2000-based computer, follow these steps:
 * 1) Click Start, point to Settings, click Control Panel, and then double-click Regional Options.
 * 2) Click the General tab, and then under Language settings for the system, click to select the check box (or check boxes) next to the language (or languages) that you want to install.

To set the user locale on a Microsoft Windows XP-based computer, follow these steps (using the Classic Start menu):
 * 1) Click Start, point to Settings, click Control Panel, and then double-click Regional and Language Options.
 * 2) Click the Regional Options tab, and then in the Standards and formats section, select the location that you want in the list to the left of Customize.

To set the UI language on a Windows XP-based computer, follow these steps (using the Classic Start menu):
 * 1) Click Start, point to Settings, click Control Panel, and then double-click Regional and Language Options.
 * 2) Click the Advanced tab, and then under Language for non-Unicode programs, select the language that you want in the accompanying list.



STATUS
This bug was corrected in Visual Basic .NET (2003), Visual C# .NET (2003), and Visual J# .NET.



Steps to Reproduce the Problem

 * 1) Create a new Windows application in Visual C# or Visual Basic .NET.
 * 2) Change the default name of the project to something in Unicode. (To obtain alternative code page characters, start Windows Explorer, click Start, point to Programs, point to Accessories, point to System Tools, and then click Character Map.)
 * 3) Press F5 to build and run the project.

The application runs with no errors. Stop the application.
 * 1) Now try running the application by pressing CTRL+F5 (start without debugging).

The application returns the error message described in the &quot;Symptoms&quot; section of this article.

