Reputation: 953
My VS2013 Professional just stopped showing build errors in my error list (which is more user friendly as i can click on errors and go straight to the offending line). Build errors e.g non-existent method on an object now only show up at build time in the Output window. This is proving to make my life harder as i now need to run the project every single time, to see errors which i should really get in the error list before runtime.
I have tried
And nothing is working.
Maybe iam just confusing VS2013 with another IDE, but iam pretty sure VS2013 is suppose to show errors in the Error List when build fails with errors such as
C:\Users\User\Documents\Visual Studio 2013\Projects\MyProj\UI\Main.cs(149,213,149,221): error CS1061: 'Helper.Track' does not contain a definition for 'location' and no extension method 'location' accepting a first argument of type 'Helper.Track' could be found (are you missing a using directive or an assembly reference?)
which are wrongly showing only in my output window.
Upvotes: 9
Views: 10388
Reputation: 109
If I select the Solution in the Solution Window, right click Solution and select either Build Solution or Rebuild Solution, the errors and warnings show up in the error list.
Upvotes: 0
Reputation: 1
Had this problem with xamarin project in vs 2015. Opened a non Xamarin and the error list worked fine. Then reopened the xamarin project and now the error list was started to work in it also. So the solution for me was to open non xamarin related project.
Upvotes: 0
Reputation: 2844
Restarting Visual Studio did the trick for me. Seems to also have worked for one of the contributors to this Microsoft Social post. I had tried all the answers on this page to no avail.
Upvotes: 1
Reputation: 31
I'm seeing this in 2015 every once and a while. For me changing the "Show issues generated" drop down gets them to show up. Even if I was already on "Build + IntelliSense", dropping it down to "Build Only" or "IntelliSense Only" can get them to display (without having to rebuild). Sometimes I can take it back to B+I and keep the revealed errors, sometimes not. Rather weird.
Upvotes: 3
Reputation: 2325
I had this problem with VS2015 Update 3 RC and Xamarin (.Forms shared project).
Compiler don't stop, errors were only showed in the output window.
This only for Xamarin projects (with VB.NET projects all has worked as expected)...
To try find the reason for the problem, I have changed the Build Output in VS:
After doing that, the compiler has stopped and the error was showed..
After that, I have set the option back from "Diagnostic" to "Minimal" (like it was before) and... it has worked also with "Minimal" (to be sure, I also have restarted VS)...
So.. it seems that only to change (touch) the setting (MSBuild Output Verbosity") has solved the problem and that this is a bug in VS and/or the Xamarin integration Software...
Upvotes: 1
Reputation: 61
Right hand side of ErrorList, select Build + Intellisense. Worked for me
Upvotes: 6
Reputation: 40223
Had this problem for ages, just worked it out.
Your problem is over 6 months old, so I assume you've worked it out, but for others, make sure the dropdown list in the top left corner of the error window (next to the error count, under the text 'Error List') is set to 'Entire Solution'.
Mine was set to 'Current Document'.
Upvotes: 2
Reputation: 2512
Make sure that you have Build + Intellisense
selected within the Error List
pane. By default on VS2015 it is set to Build Only
Upvotes: 0
Reputation: 235
Go to the view menu and select Errors List. That's what you're looking for.
Upvotes: 0