Many of us experienced Visual Studio becomes unresponsive when we are do coding. The Visual Studio IDE gets slowdown to the extent where developer cannot even see the typed characters or intellisense instantly on the code editor window. After few seconds the IDE gets hang.
Visual Studio slow intellisense:
Typically, You may try rebooting the Visual Studio IDE several times thinking that it will help in releasing memory or cache. You may also try deleting temporary files from %temp% folder and so on. If nothing worked out then you finally end up rebooting your computer. Later after sometime you will observe the same behaviour where Visual Studio again becomes unresponsive when you type any text on the code editor. In this article let’s see how to solve Visual Studio slow intellisense problem.
This is the ideal problem existed with the early version of Visual Studio IDE 2005 and 2008. This happens when .NCB file gets corrupted. Basically, the NCB is a file extension for a database file used with Microsoft Visual Studio. The term NCB stands for Non-Compiled Browse file which contain information about symbols used in a C++ program, as well as user-defined classes.
NCB files are used by Intellisense which is the component of Microsoft Visual Studio that allows code auto completion. An NCB file also includes information that is used by ClassView and the WizardBar are basically components of Microsoft Visual Studio. Suppose if NCB file gets corrupted, then Visual Studio failed to load the intellesence. In this case user will experience the slowness.
In order to solve Visual studio slow intellisense problem you can execute the below workaround solution.