Visual Studio 2005 Beta 2 Won't be the End of March!

In this week's CodeGuru newsletter, I posted an editorial titled "Visual Studio 2005 Beta 2 'Release Date' Confusion". I include that editorial here.


Unfortunately, people want dates. They want to know when to expect things. Up until now, Microsoft had been stating that Beta 2 of Visual Studio 2005 would be released by the end of March. As such, most people assumed that it would release March 31st and start showing up the first week of April.

The first week of April has come and gone. April 1st is April Fools day. Maybe the joke is on all of us!

This past week, one Web page on the Microsoft site does give implications as to when the beta will be released. This page on Microsoft's site is counting down to a release on the 25th of April. Unfortunately, this is not — repeat, not — a countdown to the beta. Rather, in talking to several people at Microsoft, this is a countdown to a new program - the Beta Experience Program.

http://nl.internet.com/ct.html?rtr=on&s=1,1j2z,1,7b3c,1abl,jorm,i5r0

Will the 25th of April be the day the beta is released?

I've asked about the page and the date. The official answer as of yesterday was that there was not a set release date at this time for Beta 2. Rather, I was told that the latest code drops are in the final stages, and that Microsoft will ship the beta when the criteria for a "Go Live" release have been met.

"Go Live" is — in simple terms — is a way for developers to be able to deploy applications created with Visual Studio 2005 Beta 2 without violating any licensing agreement. If you read the licensing agreement on the beta, you are likely to find that you are not allowed to put any applications into production use. "Go Live" allows a way for Visual Studio 2005 beta applications to be launched onto the Web.

So, in summary, there is confusion as to when Beta 2 will be released. It isn't going to happen by the end of March. Will it happen by the 25th? No official confirmation has been given; however, things are looking like the release will be very soon. Personally, I'd rather wait a few extra weeks and know that the product will be much more stable!

If you look at the above page, you should also be forewarned that "6-weekly" means every six weeks. It does not mean "once a week for six weeks". More than one person has been confused by that statement already!

# # #



About the Author

Bradley L. Jones

bjones@jupitermedia.com

Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Companies undertaking an IT project need to find the right balance between cost and functionality. It's important to start by determining whether to build a solution from scratch, buy an out-of-the-box solution, or a combination of both. In reality, most projects will require some system tailoring to meet business requirements. Decision-makers must understand how much software development is enough and craft a detailed implementation plan to ensure the project's success. This white paper examines the different …

  • By providing developers with the right tools to detect, understand, and fix problems early, your business can simplify software development, shorten development lifecycles, and improve the quality of software code. The end result is increased innovation, secure applications, and a faster time to market — all at a lower cost.

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date