Sign in to follow this  
DrGUI

[.net] When will VS 2005 come out?

Recommended Posts

I want to know when VS 2005 comes out so I can use all of the exciting features like generics! I know there's a beta version but you have to go through so much stuff to actually get to it, and anyway it wants you to uninstall beta 1 first. Since I've forgotten the Administrator password, I'm screwed! No point in rebuilding the computer when I'm supposed to be getting a new one soon lol!

Share this post


Link to post
Share on other sites
As far as I know, there's no official release date for now. So, as usual, the answer is: "it will be available when it's ready" (and very sadly, probably even a bit earlier).

No other Beta after beta 2 is expected. Officially, all Ms do now is fix all the bugs, and make sure everything work nicely. (Plus finish some small features.) No big changes are done anymore.

I think you can expect RTM for the last quarter of this year.

Have a nice day,
jods

PS:
RTM will also require you to remove Beta 1;
If you have Beta 1, you should be able to use generics ;-)

Share this post


Link to post
Share on other sites
Word is that it should be out somewhere around September 2005, but that's not an official release date. Judging by the stability of the current betas however, I guess the date is reasonable.

-Markus-

Share this post


Link to post
Share on other sites
I agree that it's very stable. But the base librairies are full of bugs. After just one month of light usage, I've reported 4 unique bugs. And it looks like I'm not alone: there are tons of bug reports! Looking at it right now, there are 1532 active bugs, 452 bugs being filed last week.

But septembre is possible... let's hope!

Share this post


Link to post
Share on other sites
Thanks for the replies guys!

Are the bugs in the base libraries only in the new bits? (methinks I only use System.Drawing, System.IO, System.Math and some of the exceptions anyway, oh, and the data types)
And do they keep on updating the download with the bug fixes?

*crosses fingers for september*
But I was hoping for earlier! I'll be starting in sixth-form then with 5 AS-levels, friends and community service to do! I won't have any time for programming then!
Perhaps I could get around that by doing community service in a new club I would start up, to teach programming to strange people like my brother and his friends? Do you think that's a good idea?

Share this post


Link to post
Share on other sites
DrGUI, yes the bugs usually are in the new bits. And they usually aren't critical ones. I could find a workaround for every bug I found in beta 2 (which was not the case in beta 1).

But no, Ms doesn't keep pushing bug fixes. Remember it is a beta, and as such you are warned that it does contain bugs. Bug fixes will be available with the RTM. (or with CTP, if there are any to come (probably)).

VS 2006 ? :-) Didn't the same thing happen to Win95 ?
Honestly, I think that VS will ship this year, even if it's late this year ;-)

Share this post


Link to post
Share on other sites
Quote:
Original post by jods
VS 2006 ? :-) Didn't the same thing happen to Win95 ?


Windows 95 was launched here in the states on August 24th, 1995. Many computer stores (like CompUSA) were opening at midnight just for the release. Hundreds of geeks were waiting outside for their copy (myself included).

Anyways, I agree that the compiler is very stable but the framework libraries, especially the System.Data library and wizards, are very buggy. In fact, our company decided not to port our 125,000 line database application to 2.0 because of the shear number of problems getting it to compile under 2.0 Beta 2 (all DataSet and databinding related). Ironically, it compiles and runs flawlessly without warning or error under 2.0 Beta 1.

Several breaks in compatibility that I reported to Microsoft were classified as being "By Design". I cannot afford to debug and redesign the data access layer of a 125,000 line app. If Microsoft ignores this break in compatibility, most developers will remain in with VS 2002 or VS 2003.

There are also several critical features/bug fixes missing that were cut out of the final product:
1) The data wizard still uses @@IDENTITY instead of SCOPE_IDENTITY() in the T-SQL code it generates for data adapters. If your table has a trigger that inserts into another table, the wrong identity is retured.
2) The introduction of nullable types is useless with database apps because the code generator for Typed Datasets does not support nullable types. You still need to call IsFieldNull() and SetFieldToNull() methods. To support nullable types with Typed Datasets naturally, you must code the dataset yourself.
3) The data wizard still ignores the presence of a ROWSTAMP/TIMESTAMP field to use for optimistic concurrency. Instead, it still passes the original values for all the fields to be checked in a DELETE or UPDATE statement. Of course, if you use BLOB fields such as NTEXT, TEXT and IMAGE, they will never get checked since you cannot compare them using T-SQL.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this