Visual Studio 2010 IDE build fails mysteriously without errors or warnings

Question

If I try to create my .sln file in visual studio (using the release configuration, but none of my configurations actually build), the assembly will fail with zero errors in the output window and not a single list of errors. In fact, in the build output window, I have 7 projects. And with normal verbosity, I have 7 "Build successed". lines after each project. But below:

========== Build: 6 succeeded or up-to-date, 1 failed, 0 skipped ========== 

Creating projects one by one, I found the project "failing", and I tried to build it on my own. It depends on another project, and it builds just fine on its own. I try to create a failing project on my own and I get zero errors and no warnings and builds failed. However, in the bin folder for this project (if I delete the old bin file), I get a built-in dll. It doesn’t do much good for me, though, since the assembly doesn’t work, the visual studio makes no effort to run my project in debug mode.

Here's something puzzling: on the command line, I went to the directory with my .sln file in it, and then ran this command:

 C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe /ToolsVersion:4.0 /p:Configuration=Release 

Then, in bin / Release, voila, I have my project built. The line runs on the command line, but not in the IDE.

Does anyone have any suggestions? This problem happened to me twice: once on Windows Server 2008 and once on windows xp sp3.

Answer 1

Visual Studio 2010 says the build failed without errors after changing the source file

One of the answers suggested that I change the place I'm building from. Here's the debug directory path:

C: \ Users \ Isaac \ Documents \ Visual Studio 2010 \ Projects \ checkout \ Library Projects \ BaseSystemCore \ BaseSystemCore \ bin \ Debug

Just dragging the validation directory to c: \ did the trick. Something related to the fact that the assembly path is too long.

Answer 2

I had the same error, it was not built, but there were no errors. Rebooting the visual studio worked for me, it was in visual studio 2012.

Answer 3

Close Visual Studio. Run cmd and enter: C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ msbuild.exe / ToolsVersion:4.0/p: Configuration = Release yoursolution.sln Then enter VS again and run the project. Worked for me!

Answer 4

If your solution contains too many projects,

build projects individually

Check which project is not working

for this project, check the links to this project, if any link, if they are marked in yellow, then delete this link and add it again, then create and verify

it will work

or

check the output window, each line, in some line that it can show, the dependency is theirs, but the file does not exist

this is a problem causing

this may be due to file corruption