Errors are ( sometimes not listed ) about wpfnewprojectsystemsample HOT 15 CLOSED

ok. I'll try that.

I've also opened an issue with Visual Studio.

from wpfnewprojectsystemsample.

Ok. Can you please vote the issue up in the feedback window then. ( btw I got the resharper errors working ) thanks for the tip

from wpfnewprojectsystemsample.

Hi,
I also has this issue. When I disable XAML building it reports the errors properly (so it seems to be related to building of the intermediate (.tmp_proj) project for XAML). I don't know if there are any workaround for this issue :-(.
I'm using ReSharper and with it I don't have this issue. All the errors are reported properly. It seems ReSharper uses it's own errors provider or something like that.

Regards!

from wpfnewprojectsystemsample.

Have you enabled "Resharper Builder"

or am I missing a trick.

from wpfnewprojectsystemsample.

Wierd. Now Visual studio shows the error

temperamental little beast of an IDE it is.

from wpfnewprojectsystemsample.

No... I changed

to

That's what made it work

from wpfnewprojectsystemsample.

I don't use this ReSharper Build feature.
I only set this setting

But not sure if it's related, but it works for me very well.

Regarding your last message where you set reporting to "Build + Intellisense" - there is a problem - the IntelliSense errors are only from the files processed by it, i.e. from opened documents. If you close the document and rebuild, you will not see the errors.

from wpfnewprojectsystemsample.

I have that also set to do not call MSBuild

from wpfnewprojectsystemsample.

@bradphelan, I mean I never using VS "Error list" and instead using "Errors/Warnings in Solution" from ReSharper (solutionwide analysis).

from wpfnewprojectsystemsample.

But I normally leave solution wide analysis off as it slows down VS. I have 65 open projects and it grinds. But that was a couple of R# versions ago. I'll try it again

from wpfnewprojectsystemsample.

@bradphelan, yes, it slows down everything, but very useful :-).
I hope VS team will address this issue. We need this feature to be working too as most of our customers (modders of our games, actually) will not have ReSharper.

CC dotnet/project-system#1467

from wpfnewprojectsystemsample.

@bradphelan would it be possible to provider a link to the feedback item so we can vote on, too?

from wpfnewprojectsystemsample.

@BrunoJuchli it's there https://developercommunity.visualstudio.com/content/problem/121523/build-errors-do-not-show-in-the-errors-list.html

from wpfnewprojectsystemsample.

My current work around is to

(1) ditch the errors list
(2) Set the msbuild output to minimal
(3) Install VSColorsOutput extensions

All the errors are highlighted in color and you can still click on them to go to source.

So it is clear that one part of visual studio can parse out the errors and another part cannot.

from wpfnewprojectsystemsample.

Please check the latest version I've just updated. Includes some new workarounds and fixes.
It seems the issue is resolved now.

from wpfnewprojectsystemsample.