I would like to hear dialog on VB2005 vs. VB2003

  • Thread starter Thread starter SStory
  • Start date Start date
S

SStory

What do most of the group think about 2005 in comparison to 2003?

Slower?

How painful is it to upgrade decent sized 2003 apps to 2005? Are there more
gotchas?

Past experience has shown me that being an early adopter of MS stuff can be
hazardous to your sanity, so I have held off.

I have played with the express version a bit. I do like generics and edit &
continue. I have read, at least several months ago that 2005 was really a
lot slower. I need to hear from people who have been using it for quite
some time now and on decent sized applications.

TIA,

Shane
 
Everything I've upgraded has been pretty smooth.

It is a lot slower in my experience. Keeps freezing trying to do the
compile as you edit to show you what is invalid, or popping up intellisense.
The designer is pretty slow too.
 
SStory

In my opinion is VB2005 for the windowsform much nicer but as stable as
version VB2002

The VB2005 webform part is for me as well great, however for me as well
overengineered (DATA part) as somebody wrote in this newsgroup. I miss in
that nice designing parts as was told that there would be, but those where
not in VB2003 as well.

For the rest see the comment from Marina.

Cor
 
Thanks Cor.

I have played with Express version and there are a few new goodies, but I
certainly don't want to deal with slower and also risk breaking my build on
a product that is ready for testing and then shipping.

-Shane
 
VS 2005 IDE is very slow -- and has some serious resource demands in terms
of CPU power and memory (2GB min).

The final output of VS 2005 (Windows Forms app) is not too bad -- the
interface is much more responsive when you make a "release build" and run
the EXE (not within VS 2005). A good indication that you know there is a
GUI performance issue with .NET 2.0 Windows Forms app is when you see many
"GUI performance" tips articles on the Start page from within VS 2005.
Group frames seem to cause all kinds of performance issues.

Continue and Edit -- still no where near as useful as VB6 debugging. There
are still a lot of things you can't do with Continue and Edit.

There is a ton of relatively useless "zero code" templates -- maybe good for
learning, but any serious development would not make use of "zero code"
templates.

If you're migrating web projects over, it will not be clean and simple
unless your projects are very basic. Windows Forms apps in 2003 migrate
relatively well to 2005 -- but you may or may not get a lot of "warnings"
(for the most part these can be ignored and/or resolved at a later date).

Lots of pretty obvious bugs in the VS 2005 IDE -- surprised they made it
thru to a "released" version.

Generics are good in VS 2005 and code snippets are nice. New pre-compiled
web apps do seem a little faster. ClickOnce is much improved.

I heard a rumor that a patch is expected in Q3 for VS 2005. I'd hold out
for the patch in Q3 before you do a full migration.
 
Back
Top