I need a reality check. Is anybody else noticing that while in the code editor in VS 2005 and pressing Ctrl-S to save or otherwise forcing a context switch (switching source files) VS.NET will take forever to return control to you?
What I see is that anytime I save or switch views VS starts thrashing the disk hard, and the CPU goes to 100% for about 10 seconds before returning control back. This gets really annoying if you're jumping around between codefiles frequently. And lest you think this is on huge files - it's not. The files I'm editing are barely breaking 100 lines of code.
I realize there's a lot going on in the editor behind the scenes with Intellisense, AutoComplete, SmartTags and all that other very useful stuff, but I think this must be related to the reformatting of the document when it first loads or reloads into the editor.
VS seems fine if you're just heads down coding on a single document and don't save frequently. At first I thought this might be one of my add-ins, but I turned off and uninstalled all add-ins that are active in the editor (like CodeRush and Refactor!), but I see the same behavior still... In fact I asked about this in the CodeRush forum, but it was apparently pre-mature since this appears to have nothing to do with CodeRush.
I'm running:
VS.NET 2005 Professional Release
2.2 Ghz P4 M (older) Dell Inspiron 8500 (yeah, I’m working on a newer box <g>)
1 gig of memory and a 7200 rpm drive
Working in the C# code editor.
The machine is otherwise working plenty fast and it's also running well in VS 2003. The VS.NET install was to a clean machine.
Anybody else seeing this and if not any suggestions what could be causing this?