Is Whidbey already dead?

M

MyMaxWebMail

Hello all,

I was just reading the Blog by Mike Harsh:

http://blogs.msdn.com/mharsh/archive/2004/09/20/231888.aspx

and it seems that Whidbey is already obsolete, even though Microsoft
has not released it yet.

Am I missing something here...

I have been using .NET (C#) for about 2 years now, and I can say with
confidence that it is the best development platform I have ever used.
We have just completed a two year migration project in which we moved
over ten years of legacy microsoft code to .NET. The resulting system
proved to be a stable one and I have never had this much fun designing
windows applications. However, I can't believe MS is already leaving
this new technology behind...

It is very frustrating because I truly believed Microsoft had finally
developed a platform that was stable, robust, and extremely easy to
learn and use. Maybe I should just get out of IT altogether...I am
really getting tired of this crap.
 
H

Herfried K. Wagner [MVP]

http://blogs.msdn.com/mharsh/archive/2004/09/20/231888.aspx

and it seems that Whidbey is already obsolete, even though Microsoft
has not released it yet.

How do you come to this conclusion? Windows Forms are supported for 10
years after the release of Whidbey, and maybe even longer if they remain
included in the .NET Framework and VS.NET. A problem would arise if
Microsoft suddently removes the Windows Forms designer from Orcas, the
version of VS.NET after Whidbey. However, it's very unlikely that this will
happen.
 
J

Jon Skeet [C# MVP]

I was just reading the Blog by Mike Harsh:

http://blogs.msdn.com/mharsh/archive/2004/09/20/231888.aspx

and it seems that Whidbey is already obsolete, even though Microsoft
has not released it yet.

Am I missing something here...

Well for a start, you're equating Whidbey with Windows Forms - I don't
see why.
I have been using .NET (C#) for about 2 years now, and I can say with
confidence that it is the best development platform I have ever used.
We have just completed a two year migration project in which we moved
over ten years of legacy microsoft code to .NET. The resulting system
proved to be a stable one and I have never had this much fun designing
windows applications. However, I can't believe MS is already leaving
this new technology behind...

They're not. From the article:

<quote>
So if you write an app on top of Whidbey, you'll be able to call PSS
about issues until around 2015.
</quote>

Not adding new features etc isn't the same as leaving technology
behind.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top