When I try to build my solution in Visual Studio (2010 SP1) containing a website, I get the following funny error.

当我尝试在Visual Studio（2010 SP1）中构建包含网站的解决方案时，我得到了以下有趣的错误。

------ Build started: Project: C:\...\Web\, Configuration: Debug Any CPU ------
Validating Web Site
: Build (web): Illegal characters in path.

Validation Complete

There is no more info whatsoever, even when build verbosity is set to diagnostic. I've tried to delete all the temporary files I could find, to restart everything I could. I even refetched my whole svn folder from scratch and rebuilt.. error still there. Then, quite randomly, the error disappeared. Now, about a day later, it's back.

没有更多的信息，即使当构建详细设置为诊断。我已经试着删除我能找到的所有临时文件，尽可能地重启所有东西。我甚至从头开始重新获取我的整个SVN文件夹并重新构建。错误仍然存在。然后，相当随机的，错误消失了。现在，大约一天后，它又回来了。

1. Have you ever experienced a similar behavior ? Could that be a bug of VS ?


2. Is there a way to increase the verbosity of the Web Site validation step so that I would see more info about the error ?

优秀答案推荐

After hours of troubleshooting I tried to debug visual studio with another instance and get to the internals of the exception. As a result, I have found the actual reason of the error :

经过几个小时的故障排除后，我尝试使用另一个实例调试Visual Studio，并了解异常的内部情况。结果，我找到了错误的实际原因：

It happens when a path containing question mark is set as a base path for the web server deployment, i.e. under

如果将包含问号的路径设置为Web服务器部署的基本路径，即在

• web project's property pages (Shift+F4)


• tab "Start options"


• section "Server", value "Use custom server" with a "Base URL"

An example of an invalid path is http://localhost/v8.0/xyz?user=User1. The reason is that the build process adds an additional slash at the end. Unfortunately VS is quite persistent in using the old setting value, so one has to restart it before rebuilding.

无效路径的一个示例是http://localhost/v8.0/xyz?user=User1.原因是构建过程在末尾添加了一个额外的斜杠。不幸的是，VS非常坚持使用旧的设置值，因此在重新构建之前必须重新启动它。

If you are facing this problem after pulling from git , then you can follow it:

如果你在退出git后遇到这个问题，那么你可以遵循它：

Step 1:

go to obj\Debug folder then find yourProject.csproj.FileListAbsolute.txt file
open it then delete what you found in building the project.
In my case i found ====>Head problem in building the project.
it followed the above step , and my problem solved.

转到obj\Debug文件夹，然后找到您的Project.csproj.FileListAbsolte.txt文件，打开它，然后删除您在构建项目中找到的内容。在我的例子中，我发现了建造这个项目的主要问题。按照上面的步骤，我的问题就解决了。

Step 2:

delete obj folder then rebuild the project.

删除obj文件夹，然后重建项目。

In my case - move solution to place with short path and use latin characters.
Example:

在我的情况下-移动解决方案的地方与短路径和使用拉丁字符。例如：

C:/Projects/MyProject/

Possible solution (found here, russian language):

可能的解决方案(可在此处找到俄语)：

1. Create folder with simple and latin-only path - for example, c:\Temp


2. (Assuming you're using Win7) go to Control Panel->System->Advanced System Settings->Advanced->Environment Variables


3. Change "TMP" and "TEMP" variables from "%USERPROFILE%\AppData\Local\Temp" to "C:\Temp" and press OK in all open dialogs


4. Restart Visual Studio

I had the same problem with Visual Studio Community 2013, with Windows 8.1 (brazilian portuguese). Change of "TMP" and "TEMP" variables works fine for me.

我在使用Windows 8.1(巴西葡萄牙语)的Visual Studio Community 2013上也遇到了同样的问题。更改“TMP”和“TEMP”变量对我来说很好。

I encountered the same error in VS 2013. The issue for me was on the project properties -> Web (tab) there is ProjectUrl. this was pointing to wrong url

我在VS 2013中遇到了同样的错误。对我来说，问题出在项目属性上->Web(选项卡)有ProjectUrl。这指向错误的URL

I encountered the same symptoms with VS2015 Update 2 while working on a WIX installer. I had unloaded the .wixproj file, edited it and tried to reload it. VS claimed there was an illegal character in some path.
No information was provided about the location of the illegal character.

在开发Wix安装程序时，我遇到了与VS2015更新2相同的症状。我已经卸载了.wixproj文件，对其进行了编辑并尝试重新加载。VS声称在某条小路上有一个非法角色。没有提供关于非法角色所在位置的信息。

I backed out my change and again tried to reload the project. Same problem.
I found I had to close the solution and reopen it before the project would reload. Or simply restart Visual Studio.

我收回了我的更改，并再次尝试重新加载项目。同样的问题。我发现我必须关闭解决方案并重新打开它，然后才能重新加载项目。或者简单地重新启动Visual Studio。

I was using VS 2019 community. There were two Visual studio opened. I had problem with one of them. When I was closing and re opening the visual studio it didn't solved until I closed all visual studio windows and reopened them again.

我使用的是VS 2019社区。有两个Visual Studio打开了。我和其中一位有过节。当我关闭并重新打开VISUAL Studio时，直到我关闭所有VISUAL STUDIO窗口并重新打开它们，问题才得到解决。

I had similar issue in Visual Studio 2019 when or after loading the solution file.The symptoms were -

在加载解决方案文件时或之后，我在Visual Studio 2019中遇到了类似的问题。症状是-

1. Some folders under that project were not loaded.


2. There was a red x mark on one folder and its sub folders.


3. There was an yellow exclaim mark on the Analyzers and Packages in the Solution Explorer.

I saw that another program (OmniSharp-vim or the OmniSharp-Roslyn server) had created a folder in the project directory with a really long name like Micorosoft Windows [Version 10.0...... git add also complained. Screen is attached below for reference.

我看到另一个程序（OmniSharp-vim或OmniSharp-Roslyn服务器）在项目目录中创建了一个文件夹，其名称非常长，例如Micorosoft Windows [Version 10.0. git add也抱怨道。屏幕随附于下方以供参考。

Once that folder was removed or deleted*, VS2019 worked normally like before.

一旦该文件夹被移除或删除*，VS2019就会像以前一样正常工作。

My problem was I accidentally put my "Command Line Arguments" in the "Working Directory" in my debug settings.

我的问题是我不小心把我的“命令行参数”放在了调试设置的“工作目录”中。

Try deleting obj and bin folders from your root folders and rebuild.

尝试从根文件夹中删除obj和bin文件夹，然后重新生成。

I ran into this on VS 2022 Community. The issue in this case was that there were new NuGet projects added to the project, and the HintPaths all had a line feed added:

我在VS 2022社区上遇到了这个。本例中的问题是，项目中添加了新的NuGet项目，并且HintPath都添加了换行符：

      <HintPath>
    ..\packages\Microsoft.Owin.Host.HttpListener.4.2.2\lib\net45\Microsoft.Owin.Host.HttpListener.dll</HintPath>

Same thing with VSToolsPath. The developer that created this code was working on a Mac, not sure if that caused it to happen. Anyway, removing the line feeds fixed the problem.

VSToolsPath也是如此。创建这段代码的开发人员正在Mac上工作，不确定这是否导致了这种情况的发生。无论如何，删除换行符解决了问题。