8

This was answered for previous versions,

However in version 15 (VS2017), the same registries for increasing NormalEvalTimeout and QuickwatchTimeout are missing.

enter image description here

Ernest
  • 1,370
  • 13
  • 23
  • Having the same problem and failed to find the solution. Simply creating the registry key by hand does not seem help... – bigge Aug 09 '18 at 06:42

2 Answers2

1

For newer versions of Visual Studio, this setting was moved to settings file. You should look to modify the LongEvalTimeout, NormalEvalTimeout and/or QuickwatchTimeout properties in the following file

C:\Program Files (x86)\Microsoft Visual Studio\YYYY\VERSION\Common7\IDE\Profiles\LANG.vssettings

Where

  • YYYY is the VS version (e.g. 2017 or 2019)
  • VERSION Enterprise or Professional
  • LANG is the programming language you want to change the setting for (e.g. CSharp, VB or VC)
Fernando Margueirat
  • 81
  • 1
  • 6
  • Changing these values is not working for me in Visual Studio 2019. I'm using ANTLR4ParseTreeVisualizer. https://github.com/zspitz/ANTLR4ParseTreeVisualizer/ – Will Huang Jul 29 '21 at 01:15
0

For me, it was coming in Visual Studio 2017 and to fix that I tried this:

I enabled the following setting:

Debug > Options > "Use Managed Compatibility Mode"

enter image description here

Raghav
  • 8,772
  • 6
  • 82
  • 106
  • This completely disables features like lambdas within QuickWatch, which is typically not an option... – bigge Aug 09 '18 at 06:40