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.
Right hand side of ErrorList, select Build + Intellisense. Worked for me
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With