I'll throw in my experiences. I've had a TON of problems with VS2003 over
the last few years in the WinForms designer. I've been migrating an
80-project product to VS2005 (7 win apps, 3 of which are complex, totaling
about 12 winforms-related projects) and I've been having a very good
experience overall. 

I had to turn an option off to get it to perform better (Tools->Options,
Windows Forms Designer, AutoToolboxPopulate set to False) (which made my
experience building user controls worse as I keep having to close and reopen
VS.NET now) and I simply had to get used to Customize Toolbox taking about 4
minutes to open (I attached a debugger and watched it load EVERY assembly
from the GAC and peruse them for controls). I haven't had any designer
blow-ups that weren't "my fault" (things like putting code in constructors
of controls that wouldn't work in design time, screwing up my own control
designer code and trying to open a designer when I didn't have a supporting
library built and/or referenced).

In fact, one form that I could not open in VS2003 (the designer would delete
2/3 of all controls on it every time I opened it) opens without problem on
VS2005 now. 

The only real complaints I have now about VS2005 aren't related to the
designers at all, but instead to the IDE itself. My Add References loads
every library from the GAC when I open it (I attached a debugger and watched
it), my Customize Toolbox does the same (again, debugger) and this thing
uses about 2.5x the amount of memory VS2003 did on the same projects before
I converted them.

Adam..

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Eyvind Axelsen
Sent: Monday, November 27, 2006 7:04 AM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-DOTNET] has there been a service pack for .net 2.0?

We have a winforms project that is quite large (though not quite as large as
the one below, at least when counting the number of projects), and we use
subclassed user controls _a lot_. In this scenario, the designer is next to
hopeless, and bugs out many times a day, rendering forms "undesignable".
Almost all the other winforms-related problems described in this thread
apply to us as well.

Eyvind.

-----Opprinnelig melding-----
Fra: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] På vegne av Matthew Wills
Sendt: 27. november 2006 00:26
Til: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Emne: Re: [ADVANCED-DOTNET] has there been a service pack for .net 2.0?

J,

We converted a project from VS.NET 2002 to 2005.

Winforms, with 6 solutions (each containing around 40 projects). About 50
projects include Winforms. Mainly VB.NET, with some C#. Multiple processes,
using Remoting. Some multi-threading. Alot of COM use (mainly Word and
Excel). Web integration (authenticates to web server to download data for
the specific user).

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to