No Whidbey this year

MKlucher

See this is why Microsoft bugs me sometimes. All their development stuff: MSDN Mag, MSDN Flash, .NET Show etc.. has been dominated with all the "Cool new features" and stuff you can do in Whidbey, Longhorn and Yukon. But then they keep pushing the release back. Why don't they back of the push and give me tips on stuff I can accomplish now! I've got this cool new development language/platform codenamed "sureitdoes" where it will write code by just thinking about the program you want to make. It's slated for release sometime next year. (If you ask me next year though it might be delayed). But reguardless you should all be changing your pipelines to get ready for it now. Sigh.... X|

Kant

That's no surprise given the track record of Microsoft. All the buzz they created on these products only to attract new corporate beta testers and keep the developers on their side. :|
Promise only what you can do. And then deliver more than what you promised.
This signature was created by "Code Project Quoter".

Nitron

Now see, here we have diametrically opposed opinions about MS... Some say "oh, MS crap is so unstable... Look at all the security holes... Oh, the sky is falling, the sky is falling!!!" And yet others say "Oh here we go again... .MS delaying a release... Why don't they release the stuff and iron out the bugs later!!!" Ok, so what is the right answer? I say just wait. What is promised that you can't work-around or implement now? My philosophy: dream and research on rumors, design and implement on facts. MS is in a decent financial position to "do it right", why rush it? I would prefer slickness and stability over "good enough", and I think MS really has that at heart. It's much more difficult to make decisions when you dominate nearly 90% of the market share... ~Nitron.

ññòòïðïðB A
start

Rocky Moore

Mike.NET wrote: Longhorn delayed, 2007. Well, guess it is time to double my Prozac prescription! Rocky <>< www.HintsAndTips.com www.GotTheAnswerToSpam.com

Navin

Mike.NET wrote: Longhorn delayed, 2007. So we'll have to wait for 2007 for a new version of Internet Explorer then... Remember, even if you win the rat race, you're still a rat.

Marc Clifton

Loooooooonghorn. Marc Microsoft MVP, Visual C#

Bruce Duncan

Kluch wrote: See this is why Microsoft bugs me sometimes. All their development stuff: MSDN Mag, MSDN Flash, .NET Show etc.. has been dominated with all the "Cool new features" and stuff you can do in Whidbey, Longhorn and Yukon. But then they keep pushing the release back. Why don't they back of the push and give me tips on stuff I can accomplish now! You get a high five for that!

Searching the web without Google is like straining sewage with your teeth.
Userfriendly, 2003/06/07

Stephane Rodriguez

A few remarks: - Why is it delayed? A lot of articles out there, yet not a single message except "we delay the stuff, deal with it". wtf? - Isn't Yukon mostly a more managed version of Sql Server with the ability to host the CLR? What's the big deal? Why is it I smell so much nasty other things? Could it be the product doesn't deliver that well? - Although Microsoft claims transparency through the hundreds of weblogs out there, no one, NO ONE would ever talk about the issues causing such a delay. While I understand that none of them wants to break the corporate policy, I think it's more than useful to explain what you are doing in a reliable and predictable manner, rather than say nothing and let the PR guys do their usual brainless jobs. So much for their "transparency" and "customer satisfaction". - It seems the development products are delayed because of their dependency with Yukon, next version of Sql Server? But does this mean the guys at Microsoft will take advantage of that time to ensure backward compatibility between the .NET run-time and/or between VS.NET IDEs, provide file converters and so on? I would be striked if Whidbey shipped in mid 2005 and yet provide no backward compatibility (like VS.NET 2003 did over VS.NET 2002)? I refuse to think that the time will be spent on Longhorn instead, it would prove the "customer-go-fuck-yourself" paradigm would still be valid in Redmond.

Michael P Butler

Surely? Our development tools and platforms have been racing ahead of what our users have installed. Most of my users don't even run Windows XP and NET 1.1 yet? Yukon sounded good but most of my users wouldn't be replacing their SQL Server with it, so all the cool development features would be useless to me. Still, it sounds like I've got little reason to renew my MSDN universal subscription this year. I can barely afford it most years, but this year sounds like I won't be getting anything for my hard earned cash. Michael But you know when the truth is told, That you can get what you want or you can just get old, Your're going to kick off before you even get halfway through. When will you realise... Vienna waits for you? - "The Stranger," Billy Joel

Senkwe Chanda

Well it sucks :-) But I'd much rather they take their time and give us a less buggy product. Whidbey has alot of cool features, but it's not like Visual Studio .Net 2003 is totally hopeless today. People are still building good applications with it. Same with Sql Server. I say lets just be patient. Either that or jump to OSS where they "release early, release often" or something like that. Problem solved. :cool: Woke up this morning...and got myself a blog