Build errors are not always translated into IDE errors about tooling HOT 10 CLOSED

Impressive. I've seen this too.

from tooling.

/cc @BillHiebert @sayedihashimi

from tooling.

@mgravell do you have steps that we can use to reproduce this?

from tooling.

No, but if I do find a reliable repro, I'll push it into a side-branch (of
whatever I'm working on) for you!
On 7 May 2015 8:17 pm, "Sayed Ibrahim Hashimi" [email protected]
wrote:

@mgravell https://github.com/mgravell do you have steps that we can use
to reproduce this?

—
Reply to this email directly or view it on GitHub
#48 (comment).

from tooling.

Can we close this? In its current state we can't act on this issue.

from tooling.

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:

dnvm install latest -arch x64 -a default -Persistent -Unstable

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.

from tooling.

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.

from tooling.

I have the same issue. Does anyone have a solution?
(Visual Studio Enterprise 2015 - Version 14.0.23107.0 D14REL - Microsoft.AspNet.Mvc 6.0.0-beta6 - DNX 1.0.0-beta6 x86)

from tooling.

Should be fixed now. Please reopen if not.

from tooling.

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.

from tooling.