Visual Studio 2017 is too slow during building and debugging

In order to obtain a better performance in Visual Studio 2017, some kind of Performance Tweaks can be applied as shown below:

  1. Set Current source control … to None under ToolsOptionsSource Control

  2. Uncheck Synchronized settings across ... option under ToolsOptionsEnvironmentSynchronized Settings (for some versions: ToolsOptionsEnvironmentAccounts)

  3. Disable CodeLens (Optional): Uncheck Enable CodeLens option under ToolsOptionsText EditorAll Languages

  4. Disable Diagnostic Tools (Optional): Uncheck Enable Diagnostic Tools while debugging option under ToolsOptionsDebuggingGeneral

  5. Clean the contents in the following folders (do not delete these folders, instead delete their contents only) and restart Visual Studio:

    Clean the content in WebSiteCache folder (can be found in
    C:\Users\%USERNAME%\AppData\Local\Microsoft\WebSiteCache)

    Clean the content in Temporary ASP.NET Files folder (can be found in
    C:\Users\%USERNAME%\AppData\Local\Temp\Temporary ASP.NET Files)

Note: If you have Hardware Acceleration enabled or if you use the default Visual experience settings in Microsoft Visual Studio 2017 or Visual Studio 2015, you might experience intermittent performance issues, product crashes, or rendering issues. In order to work around these issues, apply the following settings under ToolsOptionsEnvironmentGeneral

enter image description here

For more information, visit You experience performance issues, product crashes, or rendering issues in Visual Studio 2015 and Visual Studio 2013.

If the problem is related to debugging, try the workaround on Visual Studio debugging/loading very slow.

I hope this helps...


There can be solution with priority..

1) Disable Diagnostic Tools

enter image description here

2) Disable rick client visual experience

enter image description here

3) Disable all sync setting.

enter image description here

also make sure you removed the cache by using run -> %temp%. good luck.


My problem was with Lightweight Solution Load. Once I disabled that everything went back to normal.