Re: Visual Studio Performance
Greg Robinson <[email protected]> Fri, 14 Dec 2007 10:57:43 -0500
| Newsgroups | gmane.comp.windows.devel.dotnet.winforms |
|---|---|
| Message-ID | <[email protected]> |
"One trick I learned was to close all designer and code windows before closing the solution. " Yup, we discovered that one too. Greg Robinson Custom Data Systems, Inc. www.cds-am.net -----Original Message----- From: Discussion forum for developers using Windows Forms to build apps and controls [mailto:[email protected]]On Behalf Of Charlotte Foust Sent: Friday, December 14, 2007 10:51 AM To: [email protected] Subject: Re: [DOTNET-WINFORMS] Visual Studio Performance I did find with VS2005 that you need dual-core and a couple of megs of RAM to cope. One trick I learned was to close all designer and code windows before closing the solution. VS2005 comes up WAY faster that way. One irritating habit is that if there is a designer window buried in your stack of open windows somewhere, VS will load the toolbox when you start up, and that can take a looong time. Closing all windows prevents that and gives you control much faster. Charlotte Foust -----Original Message----- From: Discussion forum for developers using Windows Forms to build apps and controls [mailto:[email protected]] On Behalf Of Greg Robinson Sent: Friday, December 14, 2007 4:44 AM To: [email protected] Subject: Re: [DOTNET-WINFORMS] Visual Studio Performance We have been fighting this for a year now. More RAM did not help. Greg Robinson Custom Data Systems, Inc. www.cds-am.net -----Original Message----- From: Discussion forum for developers using Windows Forms to build apps and controls [mailto:[email protected]]On Behalf Of Andy Langowitz Sent: Thursday, December 13, 2007 5:03 PM To: [email protected] Subject: [DOTNET-WINFORMS] Visual Studio Performance When moving from VS 2003 to VS 2005, I found that the performance of the development environment got worse, particularly when using the Windows Forms and designer. Does anyone out there have a sense yet of whether VS 2008 makes this better or worse? Thanks, Andy