Whidbey Stablility

  • Thread starter Thread starter Brandon Potter
  • Start date Start date
B

Brandon Potter

Looking for opinions on whether or not Whidbey is reliable / ready enough to
support development of some non-critical Windows Forms apps (apps that we
developers use).

Specificially, once it's compiled is .NET 2.0 pretty stable?
 
Brandon Potter said:
Looking for opinions on whether or not Whidbey is reliable / ready enough
to
support development of some non-critical Windows Forms apps (apps that we
developers use).

Specificially, once it's compiled is .NET 2.0 pretty stable?
Click to expand...
If noone here has an informed opinion, you may want to post/read where those
actively engaged in beta testing Visual Studio 2005 are corresponding:

http://communities.microsoft.com/newsgroups/default.asp?icp=whidbey&slcid=us

I'm looking at 2005 with simple classroom-style projects and it seems pretty
stable to me, but I don't think my experience is an endorsement for what you
are planning.
 
If I recall the beta licence precludes it from use in production.

Also, the framework remains subject to change until release, so what
functionality you have this week may well not work with the final version (I
can almost guarentee it!!).

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director
 
John,

Thanks for the response, although my question was not about beta licensing
or future updates... I will restate.

Last I heard Whidbey should be released in first-half of 2005. It's pretty
hard for me to create a powerful, stable application in under 5 months,
regardless of the tools used (which, to us, are the least important items
when compared to design strategy and implementation).

I may not be the majority here, but I'd rather have myself and my dev's
working with Whidbey and .NET 2 from the point that it is a relatively
stable beta, and watch what changes occur between now and release. This way,
come release date, we're already familiar with the old, the new, and the
little quirks of both, ready to apply .NET 2 technologies to our .NET 1.1
production apps. I feel it gives us a bit of a strategic advantage in
learning the technology and is worth spending the dev time on. If we happen
to come up with a good app before the release, then we might just have to
wait until the magic license fairies fly down and sprinkle the "use in
production" dust on the code before we put a 'done' stamp on it. :)

My purpose in asking is simply to find out... "are we at that point yet?"

I realize that as a MS Director you can't really, legally say "yeah! it's
stable!" until the day of release, so I'm a little more interested in people
outside of MS who have been actively beta testing -- which Peter pointed
out, might be well suited for the other newsgroup.

Thanks!
Brandon
 
Hi Brandon,

I dont actually work for Microsoft, as an evangelist for their technology,
so my views are my own to state.

ASP 2 is coming, it will be faster to develop in and better than ASP 1x. I
believe you should continue to develop your applications in 1.1 - and train
your developers in 2.0. You can make the transition easier and make them
better developers by ensuring good practice is followed - code behind, make
use of DLL's / webservices where you can and keep your interface as clean
and code free as possible - making it easier to switch your apps over.

2.0 is certainly relatively stable now, but it remains subject to change -
if you can plan for and work round any changes as the beta progresses then
you'll be ahead of the game when it does actually get released.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director
 
Back
Top