Minh T. Nguyen

        "Enemy's Gate Is Down"
Search this site:

Minh Tri Nguyen Minh T. Nguyen enderminh Vietnamese nguyentriminh blog Visual Studio .NET Tips and Tricks Nguyễn Trí Minh
posts - 203, comments - 798, trackbacks - 120

Visual Studio .NET 2005 and SQL Server 2005

It's official (although we all kinda know this by now), but Whidbey and Yukon now have official product names and release dates:

Whidbey will be called Visual Studio .NET 2005 and Yukon will be called SQL Server 2005. Both of them will be released in the first half of 2005.

Source: http://story.news.yahoo.com/news?tmpl=story&cid=581&e=4&u=/nm/20040311/tc_nm/tech_microsoft_delay_dc

Before everyone complains about why it was delayed. I dunno, I have my own opinion about this. They say that Whidbey is being released since it's so tighly integrated with Yukon, and I understand that some people (like me) care less about Yukon and are more excited about Whidbey.

However, c'mon folks, give Microsoft some time. They say that they are releasing Yukon, Whidbey, Longhorn etc simply whenever it's ready. Under no circumstances should they release software prematurely if it's simply not ready for prime time yet. On the one side, everyone complains that Microsoft produces buggy software, but on the other side we are pushing them to release stuff ASAP.

Look at your products you write at your company. You guys know how incredibely hard it is to write bug-free code. If Whidbey is released at a later time, it's for the better. I just wish I can go to sleep and wake up in 2005 to start writing master and content pages now. ;)

posted on Thursday, March 11, 2004 11:36 AM

Feedback

# re: Visual Studio .NET 2005 and SQL Server 2005

hehe, I think you are the only one that think well thought about Microsoft, lol. Linux rule!!!!!!!!!!!!!!!!

MC
PS: if you ask me why linux rule, i'll said cause every free serious tools is in it, from programming tools, to pdf stuff, to documentation, to hacker tool.
3/12/2004 5:27 PM | Minh Chau

Post Comment

Title  
Name  
Url
Comment   
Enter the code you see: