To get "supposed" bux fixes and improvements from 2002.
2003 is no better, only adds new unimpressive features. Actually only added
complexity, as there are now two versions of framework to support on clients
end--the frameworks are "supposed" to be compatible with each other, but
look at the "known issues" and it is clear they are not, in MANY respects(It
is really almost false advertising to claim they are), some/many 3rd party
stuff only compatible with one or the other version of dotnet. Once project
is "upgraded" to 2003, 2002 won't open it. Many catch 22 situations. More
than ever, and have been doing this almost 20 years.
Whidbey supposed to be real version, fixing more bugs, but we'll see.
Why not spend just a "little" more time in QA and making product more stable
to begin with. OR, at least a "service pack" every year for a year or two,
as opposed to bombarding us with buying a new version every year just to fix
things that weren't done right the first time, then finding out it doesn't
fix jack squat, really only costs money, and makes things more complicated
then they were to begin with.
"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:OI**************@TK2MSFTNGP12.phx.gbl...
Hi Art,
Why did you buy 2003 then? Did somebody force you?
--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com
"Art Vandelay" <ar************@hotmail.com> wrote in message
news:ey**************@TK2MSFTNGP09.phx.gbl... I have bought VS dotnet 2002, and then VS 2003. Now I need 2004 ASAP.
Please go ahead and charge me and get me VS 2005 ASAP as well.
You see, if I'm not able to consistently and frequently change my
development environment and get to recompile all my projects, verify
compatibility with all 3rd party software, constantly rerollout
software, etc, I find I have too much time on my hands and end up wasting
it--spending too much time with my wife and kids, etc.
Hurry up, please I'm waiting....
