I've been working with VS2005 since it was released on an older computer, it worked fine but I wanted something quicker, with more memory.   So,  I went and purchased a top of the line pc with 2 quad core processors and 4 gigs of memory with vista on it.  (my older computer had vista on it as well).  I installed VS 2005,  installed SP1, and then the SP1 Vista patch.  I opened my website that I work with every day and found that it takes 30 seconds to a minute to switch to the design view of any given form. 

During the long wait on the status bar, is says "Building Control abc..." then "Getting File web.config..." then "Building control xyz..." then goes back to "Getting File web.config..." then next control, then web.config over and over.   It used to just pop up in design view after a couple seconds on my older computer, accessing the server and files in the same way. 

The website files are stored on a web server on my network, and I access them through a mapped network drive.   I thought perhaps my network settings were not right, the new computer had a gigabit network card and thought the duplex settings were not right or something.  I plugged my computer directly into the gigabit switch that the server is is on and made sure the switch and computer were set right.   I dont know what else to try.   This new computer is Much slower than my old.  My CPUs are sleeping while switching to design view, the memory is sitting at 50% used...   I switch back and forth between source and design view a lot.  This is killing me.

 Any Ideas?

I've noticed this problem also when switching to Design View.  I read a few post on the web and found that closing the Toolbox (with all of the controls) improves the speed.  Visual Studio trys to refresh the the controls everytime when the toolbox is open. 

I tried turning off the tool box, but there was no change in the speed of switching to design mode.

Can you think of something else I can try?

These are some of the tips that I found an implemented

http://www.thekua.com/atwork/?p=29 

Generally opening Web from a network share is not a supported scenario since network share is not considered a trusted source in .NET and hence loading assemblies may throw exceptions and make process slow. You can try changing .NET security policy using CASPol.exe.

As a side note, quad processors won't help much, Design view is a single threaded editor and won't utilize more processors. another possibility is to try VS 2008 Beta 2 which has completely different designer with split view and which is able to switch views much faster.

Thanks for that insight Mikhail.  How should I be connecting to the web files?  Should I be working on a local copy and they uploading the files over the network to the server (in the server room next to my office)?   I'm just worried about having to keep track of which files I edited and which ones I need to push to the server when I'm done working, or having to push the entire, very large/complex web application to the server each time.   I dont like the idea of pushing the entire site at all, because once in a while some IT people here make small text changes to pages and I would overwrite their changes.  The current set up that I am using, notifies me when a change has been made outside of the editor and lets me reload the file with the changes.    Is there a guide out there somewhere that can help me with these questions?   I've tried all the tips you and the other gentleman offered and it is still very slow.    I will try the 2008 Beta and hope for the best for now.  But I would like to be doing this "the right way".   I have wanted to develop on my local machine for a long time, but have not because of my concerns above.  I can not debug properly at all either because it is over a network share and the site has too many files and goes over the limit that can be monitored over that type of connection.   Thanks for any advice you can give! 

It seems your environment calls for some sort of source code control system (SCC) like Visual Source Safe. SCC maintains local copy of the site, lets you 'check out' files for editing (others using SCC will know you are working on the file) and 'check in' changes with comments. It also maintains history of changes so you can always rool back if needed.

Right.  I guess I have never bothered with them because outside changes to my sites are so rare.   I am the only editor of the site I am most concerned with and do not need to use an SCC system.   What is the best way for me to work with these site files? Does visual studio keep track of the changes I make locally and upload them to the server automaticly?