-
Notifications
You must be signed in to change notification settings - Fork 124
Build errors are not always translated into IDE errors #48
Comments
Impressive. I've seen this too. |
@mgravell do you have steps that we can use to reproduce this? |
No, but if I do find a reliable repro, I'll push it into a side-branch (of
|
Can we close this? In its current state we can't act on this issue. |
I am having the same issue time to time, however do not have the exact steps to reproduce it. What I can say is that, it usually happens right after I update the runtime using the following command, restart Visual Studio, clean the solution, rebuild the solution. Command to update the runtime:
I can see plenty of errors stating that classes, namespaces, etc. cannot be found but once I click the error within the Error List pane, the errors disappear. They appear back when I rebuild. It randomly gets fixed back. |
I don't think we can close this. There still seems to be cases where you will see errors about undefined types like system.object, I was seeing it the other day on Ryan's machine. In his case, references all looked fine but there were some underlying mismatches which generated these errors during a build. |
I have the same issue. Does anyone have a solution? |
Should be fixed now. Please reopen if not. |
I have just had this error on TFS builds from a Git repository. It appears to build and my NUnit tests run in VisualStudio IDE but on TFS build NUnit is not found and the tests do not even build. This started happening when I spotted a typo in my physical folder which was named "Test" and I removed the test projects from under it. Then renamed the the folder to "Tests" to match the solution folder name and then re-added the three test projects. I do not know if this is the cause but it does sound like a good suspect. |
This usually works, but it can get into a broken state; I have not figured out the sequence that breaks it, but example:
Build output: plenty of fail:
(and so on for ... well, ages)
However, the Error List in the IDE is: 0 Errors, 0 Warnings, 0 Messages
Edit: is this possibly a "we aren't going to show more than 1000 errors in the IDE" check? If so, I suggest putting in at least one (presumably in the highest level severity encountered), i.e. in the above "There are more than {0} build errors; please see build output" (or "build warnings" in the warnings tab if only warnings were seen, etc)
The text was updated successfully, but these errors were encountered: