How to find reason of failed Build without any error or warning

Question

I have a WebApplication which contains reference to WCF services.

While building using Visual Studio 2010, Build fails without any error or warning. However building

Answer 1

I have faced the same issue recently, I also tried so many things like, restart Visual Studio, Clean and rebuild Solution, restart PC etc. (First of all make sure all the projects in your solution are targeting the same .NET version.)

But apparently nothing worked for me so I followed the below procedure;

1. Save pending changes in the project and close Visual Studio
2. Find the exact location from file explorer and find "obj" file and open it,

3. Then, delete all the included files (some files won't remove, it doesn't matter, just skip them).

4. Use run command (by pressing Windows Key + R) and type "%temp%" and press enter to find temporary files.

5. Finally, delete them all.

This worked for me, hopefully it works for your case.

Answer 2

I faced the same problem! Just delete bin folder and restart your VS. That's all. tested in VS 2013.

Answer 3

On other possibility is that Visual Studio needs to run as Administrator, this might be related to deploying to local IIS server or other deployment need.

Answer 4

Just for the sake of completion and maybe helping someone encountering the same error again in the future, I was using Mahapps metro interface and changed the XAML of one window, but forgot to change the partial class in the code-behind. In that case, the build failed without an error or warning, and I was able to find it out by increasing the verbosity of the output from the settings:

Answer 5

I had a similar problem after adding a new project (called "TestCleaner") to my solution: Build failed, no errors.

I increased output verbosity (see Richard J Foster's instructions) and searched the output for "failed". I quickly discovered which project was failing, and why: project "TestRunner" had failed with "error CS0246: The type or namespace name 'TestCleaner' could not be found" (even though no problems were highlighted in the code).

Checking TestRunner's references, sure enough the reference to TestCleaner was marked as unresolved, and the path was missing from the reference properties. Deleting and re-adding didn't fix it. Again, no explanation why.

unresolved reference

I finally discovered the cause: "TestCleaner" was using a different target framework to the other projects. It was .Net 4.5.2; the others were 4.5.

Answer 6

It's may be due difference reportviewer version in your project and VS