Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

Build errors are not always translated into IDE errors #48

Closed
mgravell opened this issue May 3, 2015 · 10 comments
Closed

Build errors are not always translated into IDE errors #48

mgravell opened this issue May 3, 2015 · 10 comments
Assignees

Comments

@mgravell
Copy link

mgravell commented May 3, 2015

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:

All packages are already installed and there is nothing to restore.
NuGet package restore finished.
1>------ Build started: Project: protobuf_net, Configuration: Debug Any CPU ------
1>-
1>  Build succeeded.
1>           0 Warning(s).
1>           0 Error(s).
1>
1>  Time elapsed 00:00:00.2370835
1>
2>------ Build started: Project: Protobuf.Tests, Configuration: Debug Any CPU ------
2>D:\Dev\protobuf-net\Examples\Arrays.cs(4,7,4,12): DNX 4.5.1 error CS0246: The type or     namespace name 'NUnit' could not be found (are you missing a using directive or an assembly     reference?)
2>D:\Dev\protobuf-net\Examples\AutoFields.cs(6,7,6,12): DNX 4.5.1 error CS0246: The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly     reference?)
2>D:\Dev\protobuf-net\Examples\AutoTuple.cs(3,7,3,12): DNX 4.5.1 error CS0246: The type or     namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
2>D:\Dev\protobuf-net\Examples\Callbacks.cs(3,7,3,12): DNX 4.5.1 error CS0246: The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)

(and so on for ... well, ages)

2>D:\Dev\protobuf-net\Examples\Primatives.cs(561,17,561,23): DNX Core 5.0 error CS0103: The     name 'Assert' does not exist in the current context
2>D:\Dev\protobuf-net\Examples\Primatives.cs(567,17,567,23): DNX Core 5.0 error CS0103: The     name 'Assert' does not exist in the current context
2>D:\Dev\protobuf-net\Examples\SimpleStream\SimpleStreamDemo.cs(317,24,317,31): DNX     Core 5.0 warning CS0219: The variable 'psClone' is assigned but its value is never used
2>
2>  Build failed.
2>           1 Warning(s).
2>        2431 Error(s).
2>
2>  Time elapsed 00:00:01.0541880
2>
========== Build: 1 succeeded or up-to-date, 1 failed, 0 skipped ==========

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)

@davidfowl
Copy link
Member

Impressive. I've seen this too.

@davidfowl
Copy link
Member

/cc @BillHiebert @sayedihashimi

@sayedihashimi
Copy link
Contributor

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

@mgravell
Copy link
Author

mgravell commented May 7, 2015

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" notifications@github.com
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).

@sayedihashimi
Copy link
Contributor

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

@CoskunSunali
Copy link

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.

@BillHiebert
Copy link

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.

@GregorBiswanger
Copy link

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)

@sayedihashimi
Copy link
Contributor

Should be fixed now. Please reopen if not.

@Robin-Murison
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants