I recently updated from Visual Studio 2017 Community Edition to Visual Studio 2019 Community Edition.
Now, if I build my solution with errors, they will show up in the build output, but not all of them will appear in the error list. It would appear only errors of open files will show up in the error list. This is incredibly annoying.
I am not alone in this issue. It has been reported many times on Microsoft's forums, but no one has a definitive solution.
I have tried a variety of solutions people suggested in those threads:
I have ensured the filters are legitimate: Entire Solution, Errors enabled, Build + Intellisense.
I have tried deleting the .vs folder and restarting Visual Studio.
I just updated to the very latest Visual Studio 2019 version. Supposedly there are many different versions of this error, happening in versions of Visual Studio all the way back to 2017. Some supposedly have been fixed...?
I have disabled parallel project loading.
I have experienced this before in other versions of Visual Studio with Razor pages. To my knowledge, that's to be expected in Razor though.
The only other factor that I severely doubt impacts anything is that it's a Visual Studio project generated by Unity editor. From what I've read, ASP.NET, Razor, Xamarin, and other frameworks have each had their own version of issue reported. Perhaps Unity is afflicted by it too, but I don't see how or why. I doubt Unity's auto-generated Visual Studio projects are that different from your standard library projects.
I have now installed Visual Studio 2019 on two separate machines, and it appears that "Full Solution Analysis" is disabled by default.
Simply check the checkbox in options and everything seems to work as it did previously:
For those using Visual Studio 2019 v16.9.1 make sure your Error List window looks something like this:
The important part for me was selecting Build + IntelliSense (previously it was set to Build Only which explains why the error list would only refresh on build).
In my case the solution was to switch off 'Tools->Options->Projects and Solutions->General->Show output window when build starts'. Even though the 'Output' window showed "0 succeeded, 1 failed" it would not switch back to the 'Error List' window even that the checkbox above 'Always show Error List if build finished with errors' should have moved it to 'Error List'. Clearly a bug in Visual Studio 2019 which was not present in Visual Studio 2017 (I just finished updating).
In my case, it was the fact that I was building under a Release profile. Once I chose Debug from the dropdown next to the Start Debugging button, it started showing my errors in the Error List after a few seconds.
In my case it was since the dependency dll was built for x86, but in the misbehaving project its reference was with processorArchitecture=MSIL
Hello recently I started using only visual studio code for my .net core 2 project.
The problem I have found is the intellisense not working as i expect in vs code.
Always after using '.' to access avaible methods and properties no suggestions appear I have to push "ctrl+space" for them to appear.
And when I push "ctrl+space" it comes with suggestions that I can't use for anything.
Linq Example for none working intellisense
Same happens when I try to access the properties of a class.
Is it possible to get intellisense that work like in normal visual studio? I have installed C# extension for debugging and intellisense.
Proof of installed plugins
Im playing with the new Visual Studio Code on Windows 8.1 and create a new project template with the yo and i could see it running on my browser, but im not able to debug it, i set a break point in some action and it doesnt hit. On the debug option of vsCode it asks for attach a debug, but i cant find how to do it.
At the VsCode website theres a paragraph saying:
Debugging
Visual Studio Code and ASP.NET 5 are in preview and at this time debugging is not supported on OS X and Linux. Rest assured, we are working hard to bring these experiences to you in the near future.
Is there something that im missing here?
Thanks.
Visual Studio Code Preview does not support ASP.Net 5 debugging now. It only supports debugging Mono applications.
https://code.visualstudio.com/Docs/FAQ#_debugging
Is there a way to step through MonoGame source code while debugging (like with the .NET Framework) without having to compile MonoGame myself? I am using Visual Studio 2013.
No. Visual Studio requires a successful compilation to enable stepping through code.
I read that there is no problem to use Visual Studio 2012 for projects written of Visual Studio 2010. I open my project in vs 2012 and start it, everything was working. I can make changes in the existing classes and pages, no problems occur. After that I decide to add new class and here nothing was working correctly:
References to the other classes, if I add DataSet and add using System.Data it is not shown like special word(in green)
No errors no warning about new classes shown by the compiler. If I write 12312312 and build no error is shown.
Errors are shown in the browser, but I strongly prefer to have a working compiler.
Do you know what is the problem and how to fix it ?
Cleaning and Rebuilding is the way to start.
For more detailed info, take a look at this post:
Visual Studio 2012 - Intellisense sometimes disappearing / broken
For the Compiler not showing errors, give this a shot:
Delete the files in this folder:
%AppData%\Roaming\Microsoft\VisualStudio\11.0\ReflectedSchemas
Pulled from Intellisense and error highlighting not working by default in VS2012