main

Microsoft Faces Late Heat over Visual Studio 2005 Quality

Daniel Fleshbourne   on 07 November 2005 - 12:20 · 41 comments & 4286 views

Advertisement (Why?)
On day of its official launch of Visual Studio 2005, Microsoft Corp. is finding itself facing some tough questions around its bug fixing policies and plans. According to some bloggers, the much anticipated release of Visual Studio 2005, which is slated to ship Monday, following a vaunted launch event here, may be going out too early. For its part, Microsoft is committing to provide a service pack for the product but not providing further details.

Some bloggers, such as Ayende Rahein, said: "It's interesting to note that nearly all those bugs were known to Microsoft, but were closed because of time constraints. I'm shocked that even after countless CTPs [Community Technology Previews] and two betas, there are so many serious-you'll-lose-work-and-tear-out-your-hair bugs in the product. Refactoring is useless the moment you've a web project, period."

View: The full story
News source: eWeek


Dupe Article

Post a comment · Send to friend Comments · There are 41 additional comments
(6 replies) #1 DiZZySpOOn on 07 Nov 2005 - 12:24
Anyone going to Birmingham, UK tomorrow?
#1.1 Kheldar on 07 Nov 2005 - 12:49
I'll be there, finally got my pass Fri morning! Talk about a close shave
#1.2 DiZZySpOOn on 07 Nov 2005 - 13:16
Got our passes a while ago, though we did think we were going to the NEC until last night... oops
#1.3 Chicane-UK on 07 Nov 2005 - 13:33
Its probably at the Motorcycle Museum? Its about 15 minutes up the road from my house
#1.4 DiZZySpOOn on 07 Nov 2005 - 13:41
Didn't that burn down?
#1.5 Kheldar on 07 Nov 2005 - 18:05
It's at the ICC, never been there before so no idea what the gaff is like but judging by the number of Chalk and Talk *what muppet came up with that?* it should be pretty large
#1.6 DiZZySpOOn on 09 Nov 2005 - 09:21
according to the marketting guff, the "chalk and talk" is a late modification. They were originally called 'Dive Deep'

Hmm.

free copy of VS2005 is pretty good for people like me, who aren't in MSDN.
#2 Airlink on 07 Nov 2005 - 12:24
Exceuse me while I roll on the floor, laughing at everyone who thinks Microsoft is capable of releasing anything that isn't full of bugs.
I'll be in the liquor cabinet if you need me.
#3 werejag on 07 Nov 2005 - 12:31
just one in the rushed to market product line of a once great company

lets introduce Visual Studio 2005
#4 DJ Prem on 07 Nov 2005 - 13:04
I do agree MS has been ignoring many bugs I wanted to go but all the slots I wanted to go were already full so not going anymore
(1 reply) #5 ThunderRiver on 07 Nov 2005 - 13:15
There is something wrong with this product... apparently even beta tester begged for it to be delayed? I meant that is totally unheard of.

Have you guys also noticed the download size? It is about 4.2 Gb ouch. Why can't they do something like with Visual Studio.NET 2003 where it is 700 Mb, and extracted size becomes about 2.3 Gb or something.

Still, I don't look up the performance from VS.NET 2005. It still uses a whole lot more CPU and memory than previous version. The only merit is the speedy .NET Framework 2.0

I developed some application based on the beta 2 of .NET Framework 2.0, and the characters all looked really pretty (with anti-alias feature).. and after I uninstalled the beta 2 .NET Framework and installed the final version, the application I compiled in Beta 2 now looked aweful. Guess I gotta recompile my program again to make it look the way it should be.
#5.1 weiran on 07 Nov 2005 - 15:58
The 4.2GB includes SQL Server 2005, SQL Server Express 2005, and the MSDN library (which is a good couple gigs on its own).
(4 replies) #6 ev0| on 07 Nov 2005 - 14:08
There is nothing wrong with the product. It's not buggy, it'a great VS, the best one yet. Half of you guys above don't even know what it is for, you trolls.
#6.1 Cy Bones on 07 Nov 2005 - 14:27
Do you use it?
#6.2 ThunderRiver on 07 Nov 2005 - 15:15
Well, how much time have you spent with the programming in VS.NET 2005? I started from the very beginning, back in the alpha phase.. what about you? Are you telling me that you have done everything you can to drag all the bugs out, report it.. and end up disappointed becuase Microsoft closed the bug because of the time constraint??
#6.3 ev0| on 07 Nov 2005 - 23:17
I do use it. I'm a C#/ASP.NET 2.0 Developer. I'm sure there are "some" bugs in it, it's a HUGE program but the above story makes it seem like a piece of crap, and seems really biased, so I wanted to come defend it, its really helped me to be more productive.
#6.4 Cy Bones on 08 Nov 2005 - 12:27
Looks like experiences will vary!

I am sure that some of the bugs will only affect a small number of users and others may affect everyone. I still find problems and bugs in software several years old even after packs, patches and updates...

If it is making you more productive and the bugs don't affect your work then good luck!

Just like my work / your work - time and financial contraints have to be taken into account.
(3 replies) #7 lbmouse on 07 Nov 2005 - 14:25
QUOTE
It's interesting to note that nearly all those bugs were known to Microsoft, but were closed because of time constraints.


Apparently MS doesn't study history. This type of business methodology is how the Japanese beat the living crap out of the big 3 Detroit auto manufacturers in the 70's and 80's. GM would ship a sub par auto knowing there was going to be a re-call down the line while Datson would scrap an entire completed shipment rather than release a flawed product to the consumer.

Guess we can all hope that Borland, Sun, or the OSS community release products that focus on quality in addition to the bottom line. Or maybe it is time for Google to release a development platform?
#7.1 ThunderRiver on 07 Nov 2005 - 15:10
Hello there...

You think studying history will get your company into lean manufacturing mindset? Dream on! Jidoka is only the tip of the iceburg. There is NO way a big company like GM can change its corporate culture to fit into Japanese mindset. The joint-venture between Toyota and GM has been going for over a decade, and nope..GM never fully implemented the concept of lean manufacturing. They know the concept alright? They just teach it in classroom..nothing more nothing less.
#7.2 rev23dev on 07 Nov 2005 - 15:11
don't count on borland

delphi 2005 was the biggest turd i've ever used. my company reverted back to 6 after that one was released.

now we're on vs2005 and everything is going fine there.
#7.3 virtorio on 07 Nov 2005 - 19:56
QUOTE
delphi 2005 was the biggest turd i've ever used.

I'll agree with that. I'd go as far to say Delphi 2005 is the most poorly designed piece of software in history.

I've also used VS.NET 2005 and it seems fine to me. I've played with it quite a bit and haven't experienced a single problem.
(1 reply) #8 altecxp on 07 Nov 2005 - 14:32
I was really hoping they would delay it another month or so. I was really hoping that this would be a giant SWEET VS, I hope they don't do Vista and Office 12 like this.
#8.1 werejag on 07 Nov 2005 - 22:46
they will do it exactly like this along with xbox360.
(2 replies) #9 balupton on 07 Nov 2005 - 15:54
Omg wot assholes, go back to 2003 if your not happy, otherwise shut up.
#9.1 aristotle-dude on 07 Nov 2005 - 18:00
OMG. We have a noob fanboy here. Listen pal. We are talking about developer tools used for developing real business systems.

Unless you happen to be a developer, you have no business commenting on this. If you are a developer, I feel sorry for whatever company hired you. Fanboyism and development do not mix.
#9.2 altecxp on 07 Nov 2005 - 19:22
Wait are you saying its OK for a company to release a shotty product as long as there is a good previous one?

Tell us where you work so we make sure not to buy any of your "ok to be shotty" products.
#10 weiran on 07 Nov 2005 - 16:00
I just ported (by hand) one of my fairly complex web services to VS .NET 2005 and SQL Server 2005, and it did crash once.

Saying that, I still get daily crashes of VS .NET 2003 even when its patched up.

IMO, the integration with SQL Server far outweighs and negative stuff...
#11 ~*McoreD*~ on 07 Nov 2005 - 16:04
Was surprised to find two bugs on the first day had the RTM. Change a ToolStripStatusLabel1's Sprint to True using Properties. In the Form, right click the ToolStripStatusLabel1 and Spring is not checked.
(1 reply) #12 toadeater on 07 Nov 2005 - 17:24
Microsoft is copying the now standard practice by game companies of releasing products too early. For game companies at least they have a semi-justifiable reason to cut corners: budgets are pretty tight for games--but what excuse does MS have for putting out crap!? How about spending some of that multi-billion cash reserve on making a good product for once?

No, at Microsoft they made their fortune by selling crap, ripping people off, and illegally destroying the competition and they don't plan on changing their business model any time soon.
#12.1 altecxp on 07 Nov 2005 - 19:24
Just like every other company is some form or another.

Don't hate the player hate the game.
(2 replies) #13 frogworm on 07 Nov 2005 - 18:10
to everyone here who is talking like they know from experience about using the final build of vs.net 2005 after reading this article, why don't you save yourself the bother and actually try it first. it is a very nice product and they really needed to get it out the door.
#13.1 altecxp on 07 Nov 2005 - 19:27
I have used it. I don't care what the deadline is I would rather have waited 2-3months for a more stable and debuged product.
#13.2 werejag on 07 Nov 2005 - 22:49
its the frogworm. master of the fanboy club.

#14 jimbo11883 on 07 Nov 2005 - 21:49
Thank god Microsoft doesn't manufacture cars, boats or planes! BOOM! Oh noes Microsoft Car crashed!
#15 jimbo11883 on 07 Nov 2005 - 21:51
*Double Post*
#16 NEOBassDUDE on 07 Nov 2005 - 22:26
Yeah I'm experiencing quite a few bugs with the newest iteration of crystal reports in vs2005.

The fields explorer will disappear and if I click on it fast enough to catch it while its still on the screen the entire vs2005 will just close. No error reporting... nothing: just dead.

This is very very bad considering I have to get this product out in the upcoming week or so.
#17 tereshchenko on 07 Nov 2005 - 22:47
Visual C++ 2005 is pretty nice and stable (though there are almost no changes in MFC and ATL). New native C++ device development is great! And OpenMP rules.
Haven't tried new C# yet...
#18 Eth on 07 Nov 2005 - 23:00
Just been to the VS Launch in Portugal. On the hands-on sessions, the VS crashed once on the speaker and in 3 diferent demos the speakers where unable to complete the walkthrough.
The VS in itself seam very slugish taking several seconds to perform evem the most basic tasks.
Also the Microsoft page for the Lauch Event said that the atendee's were going to get a complimentary full version of th VS and SQL server but they only gave out 90-day trials!
#19 dhavalhirdhav on 08 Nov 2005 - 16:25
yeah its yet buggy... and I felt its too early to realease when they announced the launch date, because when they announced launch date at that time it was soo bugy.. I was wondering how they would fix it, but then I thought they will put more resource... but yeah its still buggy.. I hope they come up with Service Pack for it very soon.. or else they will loose market on this.
#20 Nilhanth on 08 Nov 2005 - 17:41
I could probably bet top dollar that half of you here are just youths from a certain "teen" age range...judging from the vast amount of childish remarks and lack of sophistication in those remarks!

Ok! Ok! So obviously there WILL be developers commenting here, but it's sad to see so many attempting to sound like developers, when in actual fact they're simply trying to "get in on the action" so to speak.

But hey! Who am I to judge your simple spare-time activities?
#21 aristotle-dude on 09 Nov 2005 - 18:35
The fact of the matter is that a development tool should be as stable as possible. If that means they have to delay it by a few months, then that is what must be done. This decision to release was purely a marketing decision. It was driven by their decision to use a year naming convention instead of a version number. Had it not been named 2005, but rather by the version number of the release, they could have delayed until January 2006.

Most of you fanboys do not stop to consider that tools such as this will be used to develop and deploy critical business systems by inhouse developers.

If you were a construction worker, would you want to rely on shoddy tools to do your job?

Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

Advertisement (Why?)