What's the best choice?

  • Thread starter Thread starter Cor Ligthert
  • Start date Start date
C

Cor Ligthert

Max,

The beta1 version will have a follow up in the beta2 version.

Maybe that makes your decission easier to do yourself.

Cor
 
Three years, huh? I'd go with the VS 2005. That way, you can start using
generics from the beginning, which makes for some improvements in your
coding structure.

If you aren't sure about a particular new CLR call, then avoid it until the
final product ships.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
 
I would not be worried about what version of the tool but rather what
add-on's, libraries, etc I would use to deliver a product better and
quicker!
 
I have a new project to develop in .NET. The timeline for this project is
about 3 years (yes, a big project as well). I work with VS .NET 2003 today,
but I thinking use the new VS .NET 2005 for this new project, but this is
not availabe in a final version today.

May I start with a beta version, until the final (commercial) version is
released to use the new features of .NET or is best to use the 2003 version
and migrate to 2005 in many months?
 
Jim Douglas said:
I would not be worried about what version of the tool but rather what
add-on's, libraries, etc I would use to deliver a product better and
quicker!
Click to expand...

Like .NET 1.1 or .NET 2.0 ...?

:-)
 
Hello Max,

DNF 1.1 will be backward compatible but DNF 2.0 is remarkable with many new
and refined improvements. What I suggest you must do is spend the time
studying what DNF 2.0 offers so you can make wise decisions. Finally, DNF
2.0 is available in Beta 1 -- right now -- noting Beta 2 is going to be
released within several months and will include a 'go live' license for
those willing to risk deploying DNF 2.0 while still in beta.

So yes, given what you explain I would start with DNF 2.0 now.
 
Hi Max,

The current VS 2005, although looks extremely good and works 70% of the
time, id suggest sticking with VS2003 until at least beta2 comes out.
There will be many changes to VS 2005 as it moves from beta1 to beta2,
and beta2 will also include a go live license which beta1 doesnt (beta1
is for testing purposes only). You can do your basic ground work for
the project in VS 2003 and when beta 2 of 2005 does come out (which may
be soon) it would be easy to just migrate. I would look suggest you
catch up on the changes and enhancements from framework 1.1 to 2.0
though, it will help you in the eventual migration. Bottom line, VS
2005 in beta1 state i wouldnt recomment for any industrial or
enterprise app development. Thats my 2c anyways.

NuTcAsE
 
Hey max,

I went through the same decision process you are going through. I chose
Whidbey and there are issues to consider.

One is unexpected behavior, particularly in winforms layout. Whidbey has
great new design time support for rafting containers and tool strips, but
tends to be incompatible with some of the older controls, like SandBar, etc.
Also, new things keep popping up, like the MdiList control is now a property
of the strip and it requires some finesse in accessing it. Its just a new
way of doing things that if you are used to a certain way can be
counter-productive at first, but I don't think you'll regret choosing
Whidbey. The beta release is pretty stable.
 
NuTcAsE said:
The current VS 2005, although looks extremely good and works 70% of the
time, id suggest sticking with VS2003 until at least beta2 comes out.
There will be many changes to VS 2005 as it moves from beta1 to beta2,
and beta2 will also include a go live license which beta1 doesnt (beta1
is for testing purposes only). You can do your basic ground work for
the project in VS 2003 and when beta 2 of 2005 does come out (which may
be soon) it would be easy to just migrate. I would look suggest you
catch up on the changes and enhancements from framework 1.1 to 2.0
though, it will help you in the eventual migration. Bottom line, VS
2005 in beta1 state i wouldnt recomment for any industrial or
enterprise app development. Thats my 2c anyways.
Click to expand...

While VS itself may well change a lot between beta 1 and beta 2, I
don't expect the languages will change that much. I suspect it'll be
easier to migrate from beta 1 to beta 2 than to rewrite a load of code
to use generics and the other goodies from .NET 2.0...
 
Back
Top