1

The solution I typically work with contains a couple of dozen projects. When I load this solution the status line displays something like "searching #includes for additional files", with a counting up well over one thousand. This can take 15-30 seconds (machine has quad core i7, 8G RAM and SSD, Windows 7 Pro, SP1). It the spends another 15 seconds or so "updating intellisense". In spite of all this preparation, if I right-click on a function or method and select Go To Definition, I'll frequently get a dialog box with "Please wait". This can take 10-15 seconds, though usually after the first few times, the search is instant. Others working on this solution (all are local copies managed by git and Cmake, no shared disk or anything) have the same experience.

Are there settings or something that will remove or lessen these problems. Or is this what happens when a solution gets to this size?

Thanks

Llaves
  • 683
  • 7
  • 20
  • I'm afraid, there's not much you can do, other than installing Visual Studio 6. Microsoft keep improving loading speeds with each new release of Visual Studio, but cannot seem to get down to an acceptable delay, even if run on a mid-range to high-end machine, like yours. – IInspectable Nov 21 '13 at 18:41

1 Answers1

0

I don't think you can do much about it. I've worked on large solutions on Quad Code i7 with 16/32 GB RAM on Win7/XP. They tend to load slow, build slow, start slow...

I do not recall messages about Additional Includes though. Check out these pages, they may help:

msdn,

SO

Tinkering with settings might help, but be careful, as sometimes they lead to big problems and you have to restart your project.

Community
  • 1
  • 1
Roman
  • 1,727
  • 1
  • 20
  • 28