Large project slowing down IDE?

[Adam Clauss]

I have a fairly large project (over 1800 files). When I open up the solution, the entire IDE slows to a crawl. CPU usage sits at
about 50% for a couple minutes, and then everything is normal again. This happens EVERYTIME I open the solution and is getting
rather annoying. Is there anything that can be done about this?

 

[Jon Skeet [C# MVP]]

I have a fairly large project (over 1800 files). When I open up the
solution, the entire IDE slows to a crawl. CPU usage sits at about
50% for a couple minutes, and then everything is normal again. This
happens EVERYTIME I open the solution and is getting rather annoying.
Is there anything that can be done about this?

How many files do you have open within the solution? I find that if I
close all open documents before closing the solution, reopening the
solution is much faster. I haven't worked on that size of project
though (in .NET) so I don't know if it will help.

(I also don't know whether these scaling problems are fixed in Whidbey.
I really *hope* they are...)

 

[Shiva]

Hi,

Another option to try is to disable "Track Active Item in Solution Explorer"
option and see.


I have a fairly large project (over 1800 files). When I open up the
solution, the entire IDE slows to a crawl. CPU usage sits at
about 50% for a couple minutes, and then everything is normal again. This
happens EVERYTIME I open the solution and is getting
rather annoying. Is there anything that can be done about this?

 

[Jay B. Harlow [MVP - Outlook]]

Adam,
In addition to the other comments, I know for VB.NET at least, that VS.NET
2002 was slower then VS.NET 2003 for large solutions & projects.

Hope this helps
Jay

I have a fairly large project (over 1800 files). When I open up the

solution, the entire IDE slows to a crawl. CPU usage sits at

about 50% for a couple minutes, and then everything is normal again. This

happens EVERYTIME I open the solution and is getting

 

[Adam Clauss]

How many files do you have open within the solution? I find that if I
close all open documents before closing the solution, reopening the
solution is much faster. I haven't worked on that size of project
though (in .NET) so I don't know if it will help.

Very few - usually only 5 or so files open, sometimes less. I can say that it hasn't made a difference, I've tried it with NO files
open and it still is rather slow.

(I also don't know whether these scaling problems are fixed in Whidbey.
I really *hope* they are...)

Me too

Thanks for the suggestion!

 

[Adam Clauss]

Alright I'll give that a try. Although it isn't just switching between files that is slow. Just typing, or even just scrolling
up/down the list of files in solution explorer is slow.
Thanks!

 

[Adam Clauss]

Ah, sorry I should have mentioned - I am using VS.Net 2003 Professional.

--
Adam Clauss
(e-mail address removed)

Adam,
In addition to the other comments, I know for VB.NET at least, that VS.NET
2002 was slower then VS.NET 2003 for large solutions & projects.

Hope this helps
Jay

I have a fairly large project (over 1800 files). When I open up the

solution, the entire IDE slows to a crawl. CPU usage sits at

about 50% for a couple minutes, and then everything is normal again. This

happens EVERYTIME I open the solution and is getting

 

[Adrian]

Over 1800 files? I wonder if you are using the IDE as it was meant to be.

I also run into IDE problems and discovered it had to do with where the
files were located in the directory. I happened to change their location
to one nearer to the directory root so (I could back up my work easier)
and bingo! problems gone.

I have a fairly large project (over 1800 files). When I open up the

solution, the entire IDE slows to a crawl. CPU usage sits at

about 50% for a couple minutes, and then everything is normal again. This

happens EVERYTIME I open the solution and is getting