Visual studio error list shows empty results list

Question

After fixing errors and rebuilding the error list window still has empty placeholders and a count of zero errors.

This only goes away after restarting VS

It seems random, some days I dont get the problem at all with the same solution

Trying to open one of the empty errors by clicking on it gives me a "Visual studio has encountered an unexpected error." message.

Its driving me crazy. Cant find any help out there or other people reporting the same problem

Answer 1

VS gets crazy many times.

1. Make sure your version is up-to-date,
2. Delete your automatically generated .suo file(s) (resides near the solution file)

Still bad? there might be a corruption or invalidity in a XML file it tries to read or something like that.

3. Try removing temporary files and generated files. Look at this:

   https://www.google.com/?q=visual%20studio%20temp%20files%20location#q=visual+studio+temp+files+location]

4. You can try using VS Command line switches like /Log and /Out. Further more - Add switches to the MSBuild command in your project configuration. Here is the references:

   http://msdn.microsoft.com/en-us/library/xee0c8y7.aspx

   http://msdn.microsoft.com/en-us/library/ms164311.aspx

5. Try using SysInternals ProcessMonitor to see What file is opened just before the error occurs.

6. Nothing helped? Reinstall VS completely. do a full Uninstall. I suggest you backup your preferences and tools beforehand. You can do this manually or by signing in to VS with your live ID.

   http://msdn.microsoft.com/en-us/library/dn457348.aspx

Be aware - your extensions should be re-downloaded. and one of them might be the cause for all this suffering

Answer 2

Maybe this does the trick, update VisualSVN:

https://www.visualsvn.com/visualsvn/download/

Answer 3

To debug this, you can use this solution: https://stackoverflow.com/a/9589139/61883

solved it by:

1. Open two instances of Visual Studio. Open the same project in both.
2. In one instance, goto Debug->Exceptions and enable all the 'Thrown' options to stop at first chance exceptions. This will stop the debugger when the exception is generated.
3. In the same instance, select Debug->Attach to Process, select devenv.exe.
4. In the other instance, open the form to cause the exception
5. With any luck the first instance should stop somewhere that yields a more relevant exception.