upgrading from 2003 to 2005 or wait for 2008

[lacanela]

Please bear with this old dino here, who never upgraded to vs2005, the
reason being that I am soooooo comfortable working with that rock-
solid vs2003 and my development time so far has mainly been devoted to
maintenance of existing 1.1 web sites. Now the present / future seems
to have caught up with me, and this dog now has consider to 1) do the
thing and learn new tricks or 2) sit tight and wait for vs2008 and
learn a lot of new tricks at one go.

Any advice would be highly appreciated.

Trym

[Mr. Arnold]

"lacanela" <ho***********@gmail.comwrote in message
news:11*********************@w3g2000hsg.googlegrou ps.com...

Please bear with this old dino here, who never upgraded to vs2005, the
reason being that I am soooooo comfortable working with that rock-
solid vs2003 and my development time so far has mainly been devoted to
maintenance of existing 1.1 web sites. Now the present / future seems
to have caught up with me, and this dog now has consider to 1) do the
thing and learn new tricks or 2) sit tight and wait for vs2008 and
learn a lot of new tricks at one go.

Any advice would be highly appreciated.

Everyone is just migrating to 2005, for the most part. People -- companies
don't transition or move as fast as MS seems to think they will do it, by
putting this stuff out which M$ should slow down a bit. You should move to
2005. IMO, because that's where companies are headed.

I think some of this stuff in VS 2005 and future versions of VS .NET
solutions concerning the Web won't start to take affect until MS Server 2008
and Vista business workstation O/S(s) used on the Web developer's side
using IIS7 are being used.

[Cor Ligthert[MVP]]

Hi Lacanela,

It seems that version 2008 will be even more solid as vs2003, even the
second beta version is that in a kind of way. It is impossible to give you
an advice, however because you have waited that long, I should know what I
would do in your situation.

Cor

"lacanela" <ho***********@gmail.comschreef in bericht
news:11*********************@w3g2000hsg.googlegrou ps.com...

Please bear with this old dino here, who never upgraded to vs2005, the
reason being that I am soooooo comfortable working with that rock-
solid vs2003 and my development time so far has mainly been devoted to
maintenance of existing 1.1 web sites. Now the present / future seems
to have caught up with me, and this dog now has consider to 1) do the
thing and learn new tricks or 2) sit tight and wait for vs2008 and
learn a lot of new tricks at one go.

Any advice would be highly appreciated.

Trym

[Robert]

"lacanela" <ho***********@gmail.comwrote in message news:11*********************@w3g2000hsg.googlegrou ps.com...

Please bear with this old dino here, who never upgraded to vs2005, the
reason being that I am soooooo comfortable working with that rock-
solid vs2003 and my development time so far has mainly been devoted to
maintenance of existing 1.1 web sites. Now the present / future seems
to have caught up with me, and this dog now has consider to 1) do the
thing and learn new tricks or 2) sit tight and wait for vs2008 and
learn a lot of new tricks at one go.

2008 is version independant. You can make 2.0, 3.0, and 3.5 .Net framework apps with it.

Might as well wait the few months, and get it all.

With vs2005, you only get support for 2.0 framework apps.

[lacanela]

OK, Thanks all for your input.

I'll wait until VS2008, and meanwhile download a couple of those
express versions of VS just to play with. Unsure though whether both
programs can peacefully co-exist (working on different projects
obviously) or will the .net 1.1 framework get deleted / screwed up,
interfering with the funcionality of VS2003 editing of existing
projects?

Trym

[JB]

On 24 Sep, 06:19, "Robert" <[e-mail]:

"lacanela" <[e-mail] in messagenews:11*********************@w3g2000hsg.goo glegroups.com...

Please bear with this old dino here, who never upgraded to vs2005, the
reason being that I am soooooo comfortable working with that rock-
solid vs2003 and my development time so far has mainly been devoted to
maintenance of existing 1.1 web sites. Now the present / future seems
to have caught up with me, and this dog now has consider to 1) do the
thing and learn new tricks or 2) sit tight and wait for vs2008 and
learn a lot of new tricks at one go.

2008 is version independant. You can make 2.0, 3.0, and 3.5 .Net framework apps with it.

Might as well wait the few months, and get it all.

With vs2005, you only get support for 2.0 framework apps.

Hi Trym,

A bit late in the discussion but here's my opinion on that.
First of all I don't find VS 2005 a very stable development
environment (i'm using VB.NET).
But I would say wait till the new version for 2 reasons:
1) If you're gonna "learn new tricks", you might as well do it all in
one go. If you learn the VS 2005 ones, you will very soon need to
learn new ones again. So save yourself time and effort and make the
big jump... (I believe it'll be less effort to do it all in one).
2) I totally agree with Mr. Arnold that new versions are released too
quickly, but VS 2005 isn't that new any more so get VS 2008 and you'll
be up to date for longer. By the time VS 2008 / 3.0 framework
application will be the norm, you'll be in the know!

Good luck
JB

[Cor Ligthert[MVP]]

2) I totally agree with Mr. Arnold that new versions are released too

quickly,

That does not say anything about 2008, it seems that there is learned with
the to early launch of vs2005 (and vs2002 before that) a lesson.

Cor

[lacanela]

I suppose there is no guarantee that vs2008 will any more stable that
vs2005. But then again I can't wait forever (or at least until vs2008
sp1), so I will take the plunge when vs2008 goes gold. As for learning
new stuff, there will no point in going into .NET 3.X until MS moves
on the server front, as my work is basically web-related.

Trym

[lacanela]

I agree. Actually, I have a general policy of skipping every other
upgrade for all kinds of software. I that way, I avoided vs2002, for
example.

Trym