Visual Studio Error List Shows Empty Results List

After fixing the errors and restoring the error list window, there are still empty placeholders and the number of zero errors.

VS error list window

This only happens after restarting VS

It seems random, for several days I don’t get the problem with the same solution at all

Attempting to open one of the empty errors by clicking on it gives me "Visual Studio encountered an unexpected error." message.

It drives me crazy. You cannot find any help there or other people reporting the same problem.

+8
visual-studio visual-studio-2013
source share
3 answers

VS goes crazy many times.

  • Make sure your version is updated.
  • Delete the automatically generated .suo file (located next to the solution file)

Still bad? corruption or invalidation may occur in the XML file that he is trying to read, or something like that.

  1. Try deleting temporary files and generated files. Look at this:

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

  2. You can try using VS command line switches such as / Log and / Out. Next, add the switches to the MSBuild command in your project configuration. Here are the links:

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

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

  3. Try using ProcessMonitor SysInternals to see which file opens before the error.

  4. Nothing helped? Reinstall VS completely. complete uninstall. I suggest you save your settings and tools in advance. You can do this manually or by logging into VS with your live id.

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

Be aware - your extensions must be reloaded. and one of them can cause all this suffering.

+8
source share

Perhaps this is a trick, update VisualSVN:

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

+2
source share

To debug this, you can use this solution: stack overflow

I decided:

  • Open two instances of Visual Studio. Open the same project in both.
  • In one case, go to Debug-> Exceptions and turn on all the Abandoned options to stop with exceptional random exceptions. This will stop the debugger when an exception is thrown.
  • In this case, select Debug-> Attach to Process, select devenv.exe.
  • Otherwise, open the form to throw an exception.
  • In any case, the first instance should stop somewhere, which will give a more relevant exception.
+2
source share

All Articles