VS2005 is a PIECE of Garbage and is bug Ridden

[Rob Dob]

VS2005 is a PIECE of Garbage and is bug Ridden, I wonder how many others
feel the same, I am so sorry that I have moved away from VS2003,

VS2005 is unstable, and half the stuff doesn't work, Microsft has spent so
much time trying to make it simply that when you try to do something useful
with it it doesn't work...

Half the time it crashes, and menu items appear for things you cannot do.
For example, Go into component designer, or SQLDataAdapter component for
WebForms is junk, doesn't come installed, so you add it to the toolbar and
it doesn't work, it breaks webforms.

I guess this is now a good system for doing things the microsoft way, but
build anytihng decent and forget it..,

VS2005 is a WASTE of MONEY.. I advise all to NOT upgrade, grab yourself
the express additons the FREE versions, at least you won't feel so riped...

Anyway my two cents...

 

[Fred Nelson]

Hi Rob:

I had some problems with it also at first. Now I have converted two
major apps from VS.2003 and it seems to be fine for me.

Hang in there - it will get better!

Fred

 

[Piotrekk]

Perhaps you should try to buy orginal version
PK

 

[Piotrekk]

Perhaps you should try to by orginal version

 

[Karl Seguin]

Rob:
Tell us what you really think. The last thing we want here are people
holding back their opinion...

I will admit that I too run into frustrating situations. I am using an EAP
of Resharper 2.0 though, so who knows which is to blame .

All in all, I think people should give it a try, there certainly are some
issues. Keep in mind that a service pack will be released though, not right
away, but soon.

Karl

 

[Kevin Spencer]

VS2005 is a WASTE of MONEY.. I advise all to NOT upgrade, grab yourself

the express additons the FREE versions, at least you won't feel so
riped...

That's funny, Rob. I've been using it since beta 1, which *was* bug-ridden.
I am now using the RTM (since it was released a couple of months ago), in
which I've found no bugs whatsover, just waiting for the Team System final
version to come out. Works a heck of a lot better than VS.Net 2003, does a
lot more, and I wouldn't go back for love or money. I still have to from
time to time, to work on "legacy" 1.1 apps. I've written half a dozen
different applications with it, one of which is already in production and
working perfectly for about a month now. It's a Windows service that uses
the new FtpWebRequest and FtpWebResponse, the new HttpWebRequest and
HttpWebResponse, the new XSL and XML classes, and has a web-based
log-viewing application associated with it. It runs continuously, with 2
different threads performing operations at 5-minute and 1-hour intervals, 24
hours a day. It uses the System.Net.SmtpClient class to send email reports
out at regular intervals, and the new Configuration classes to leverage the
App.Config for settings and email addresses.

One of the other apps I wrote, which was last built using the beta 2
release, was a Managed Direct3D terrain and environment simulator for small
aircraft, which uses a SQL Server database, various custom classes for
storing and parsing Geographical data on the fly, and Indigo services to
obtain real-time flight and GPS data. It was a prototype demonstrated at the
NASA SATS demo in Danville, Virginia in May, and has been touring the
country at various air shows for the past 5 or so months. I haven't even had
to touch it since May.

I guess I'm just lucky.

--
;-),

Kevin Spencer
Microsoft MVP
..Net Developer
If you push something hard enough,
it will fall over.
- Fudd's First Law of Opposition

 

[Nicholas Paldino [.NET/C# MVP]]

Rob,

You are not the only one that has issues. However, you can go to the
Product Feedback center and add weight to shared issues, or register new
issues of your own. Check out:

http://lab.msdn.microsoft.com/productfeedback/default.aspx

Hope this helps.

 

[Shawn B.]

All in all, I think people should give it a try, there certainly are some

issues. Keep in mind that a service pack will be released though, not
right away, but soon.

Hate to burst your bubble here, but they still haven't released a service
pack for VS.NET 2003 (after at least 2 years), I don't know what makes us
think they'll release a service pack for 2005 anytime sooner than that,
especially considering prior to VS.NET release, Service Packs were a regular
part of life and something we could count on (or should I say "had to count
on" and weren't let down).

In anycase, I, too, have stopped using VS 2005 shortly after downloading it
from MSDN subscribers because, in trying to create simple WinForms apps, the
IDE kept crashing and amazingly, the only time in 4 years that I've ever
experienced a kernel exception of some time in Windows XP Pro (I'm using
SP2), was twice while doing something in the VS 2005 IDE (within hours after
installing it and rebooting, of course). I haven't touched the IDE since
(and haven't experienced WinXP Pro crashing since (or before, either)) and
prefer to remain in 2003 since I perceive it to be more stable, as well.
I'm dissapointed. But once I set up a more suitable virtual machine for it
I'll venture back into 2005 development, just not on my primary development
box.



Thanks,
Shawn

 

[Alvin Bruney - ASP.NET MVP]

I uninstalled resharper, that thing don't play well with studio at all. I'll
qualify that by saying it presented problems when the project was very large
with lots of post build copying. VS seemed to be unstable a lot but i knew
it must be resharper because VS was working well on the large project before
resharper. After 2 months, i'd had enough.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006

 

[Karl Seguin]

My bubble isn't burst. Microsoft has made it clear what the service path
for 2005 is going to be, namely a service pack for both 2003 and 2005 in the
first half of 2006 - that's "soonish" in my book.
http://blogs.msdn.com/scottwil/

Karl

 

[Jeff]

Re:
<<a service pack will be released though, not right away, but soon>>

Is this just your wishful thinking, or do you have some "inside" information
on this? If the latter, can you elaborate?

Thanks!

Jeff

 

[Karl Seguin]

Kevin:
I don't think it's as bad as Rob says for most people, and Idon't think it's
as good as what you say in a lot of cases. I get errors reported @ compile
time that won't go away until I shut down and reopen vs.net.

System.Net.Mail is great and all, but some of the key classes are read-only,
making them very...inconvinient. I believe it's MailAddress.... That's
besides the point anyways, as the IDE, the language and the framework
features are separate thing. I think it's clear Rob's having problems with
the IDE. Honestly, I can't say that the VS.Net 2005 IDE has brought a lot
to the table (Team System is different) other than the ability to host the
other 2 (language and framework). Refactoring and all that is nice, but
it's been something I've supplemented with addons a long time ago...

Karl

 

[Juan T. Llibre]

re:

Is this just your wishful thinking, or do you have some "inside" information on this? If the
latter, can you elaborate?

See :

http://blogs.msdn.com/scottwil/

 

[Rob Dob]

Being perfectly honest here, The only reason I went the Microsoft way
Years Ago!! was NOT because they had the best product, but because they
dictate the market, I remember being perfectly happy with Borland's Turbo
C++, its compiler blew away Microsoft's ( MSC5.0 ), it produced much faster
code. I must admit I'm new to C#, as most of my apps are written in VC++,
and I tried to rewrite one of HEAVILY mutli threaded VC++ my applications in
C#, there is no comparison in speed, .

My frustrations lie with VS2005 webform/web applications creation using c#,
I did NOT participate in the beta, I am also not really interested in using
their wonderful NEW plug and play controls, although I'm sure to many they
are useful. I am frustrated at the lack of support that exists for
DataAdapter controls.. i.e The SQLDataAdapter is no longer available by
default in the toolbox, when you add it in and then try to make use of it
my application no longer works, However if you do the same on a winform
then everything works fine, I'm only referring to the webforms and c#
within webforms. I'm referring to the larger select statement, that
VS2005 now decides that it is better to place within a .resx file which then
it doesn't seem to have recognition of at runtime, Im talking about why
should I need to lookup docks about RESGEN, unless if thats what I wish to
do.

I also don't understand why when vs2005 creates a local resouce file. resx
it does not nest it in with the corrsponding webform.., especially when
they have gone to the trouble of creating abutton for this specific use...

I also find that a lot of the lingo at Microsoft Visual Studio site, says or
use to say, "to Be Added", its a joke these are obvious areas that
Microsofts team have yet to fill in, anyway another story there..

In short I honestly at this point am sorry that I have upgraded to vs2005,
when I originally upgraded from VS6 to Vs2002 I was happy for the most part
with the exception of debug symbols no longer being supported in the same
fashion they were in vc6 , but I overcame that...

Microsoft states, that the new VS2005 should save you tons of development
time, up to this point it has just wasted days of mine,

I also don't understand why Mr Gates, Aka Software Architect, doesn't pay
someone from Microsoft to monitor these newsgroups and then help with
answering some of these questions posted, a lot of the questions posted
within this group and other microsoft groups go unanswered.

thanks,
P.S. as per updates/visual studio service packs, I have never been around
to see one.. I think the closest I've seen to an update was when they
released VS2003 and offered current VS2002 owners a free upgrade.

 

[Rob Dob]

Hi,

guess all I can say here is:, I sure didn't have to push so hard...

"If you push something hard enough, it will fall over"
.. - Fudd's First Law of Opposition

 

[Shawn B.]

My bubble isn't burst. Microsoft has made it clear what the service path

for 2005 is going to be, namely a service pack for both 2003 and 2005 in
the first half of 2006 - that's "soonish" in my book.
http://blogs.msdn.com/scottwil/

Hmm... interesting. That's good news, for VS 2005 users. But, come one, 3
years after VS.NET 2003? That's not soonish by any stretch of the
imagination. Fortunate for me, I've never experienced a defect in 2003 that
is worthy of mention (come to think of it, can't think of any at all, and I
use it 10 hours a day since the day it released).

My point? Regarding VS 2005, and my earlier remarks, I stand corrected.
There is hope after all for VS 2005 users. Oh, and, since people ask, I
have never installed a beta/rc of 2005 anywhere except in a virtual machine.
So that wouldn't be the cause for the instabilities on my main box (which
has been the most stable box I've ever used).


Thanks,
Shawn

 

[Shawn B.]

P.S. as per updates/visual studio service packs, I have never been

around to see one.. I think the closest I've seen to an update was when
they released VS2003 and offered current VS2002 owners a free upgrade.

It seems there is indeed a roadmap for service packs. Its amazing, VS.NET
2003 gets SP1 3 years after it released, but VS 2005 will get it about 6
months or so after released. I've never had a problem with 2003, I would
consider it a bona-fide release. I consider 2005 to be a beta 3 release.
For all the hype and anticipation that 2005 created (both abroad and within
me), I am most dissappointed because the things I want to do with it produce
the only kernel dumps on my WinXP Pro (SP2) box that I've ever seen when
using WinXP (been using for 4 years). And for that, I'm only using WinForms
and doing what I do everyday on 2003 without problems. Haven't used ASP.NET
yet (which incidentally, is what I do for a living but I tend to do other
types of projects at home).

Anyway, overall, I (not to contradict myself) like the changes in 2.0 and
2005 IDE is generally more productive when it works (avoid the WinForms
designer and do it by hand). For many people, mostly MVP's and MS employees
and other MS book author types, everything works fine. So perhaps its just
our particular setups that are causing the problem. Of course, there is
absolutely no other piece of software (installed 29gigs for over 14 months)
and in the past 4 years has ever caused my WinXP to crash. Not even a bad
Canon driver caused a crash, just annoyance. From now on, my 2005
development will be contained within a VMWare guest. That way my main dev
box won't be effected. I take it very personally when it starts undermining
my system stability and causes me to be paranoid about whether things will
work or whether other unknown problems will ocurr.


Thanks,
Shawn

 

[JDP@Work]

..... with so few webHosts supporting 2.0, I wish to thank Rob for posting here,
it has made my decision to stay with 03 easier.

I've grown tired of bio hacks, reg hacks and similar just to make IDE's work as
they should.

I really don't have the energy or time to fuss with giving MS feedback in their
blog, it's not my responsibility.

Perhaps if they offered a $10K prize for each valid bug, then groups of
youngsters could earn some pocket change...

MS can have my many $'s after the SP is released, and I hear posts like, "Hot
Darn, VS SP1x is Great!"

Just my "2 cents"

..... I'm listening.... chirp, squeek (porch swing needs grease), chirp.....

JeffP....

 

[Juan T. Llibre]

re:

.... with so few webHosts supporting 2.0

You mean the hosters listed here are not enough for you ?

http://www.asp.net/Hosters/

 

[Alvin Bruney - ASP.NET MVP]

I remember being perfectly happy with Borland's Turbo

C++, its compiler blew away Microsoft's ( MSC5.0 ),

DID NOT! That thing was not ready for prime time at all. Bugs bugs bugs all
over the place. I remember writing graphics applications and having to
reboot constantly. The same set of bugs had been fixed long long ago in
early versions of VS. I'm no fan of borland's turbo C++.

Wasn't that the compiler that used pascal underneath c++? (can't remember
which one did that but i'm pretty sure it was the culprit)

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006