Where is Dotnet 2004

[Art Vandelay]

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....

[Andy Kendall]

I too have this problem. I fill my spare time developing with digital
dashboard. It's so robust and useful. I simply can't understand how I ever
did without it. The problem is of course that it makes web app development
so quick and easy that I'm now getting my work done in half the time making
that relase of 2004 all the more urgent.
"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....

[Miha Markic [MVP C#]]

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....

[Steven H]

On Thu, 26 Feb 2004 15:07:18 +0100, Miha Markic [MVP C#] wrote:

Hi Art,

Why did you buy 2003 then? Did somebody force you?

it is all new and shiny - i like shiny things ;)

--
---------------------------------------------------------
Steven H - B.I.T. Otago Polytechnic, Dunedin, New Zealand
..net Geek

[A.A. Fussy]

I have not seen a offical product name-that is VS.NET 2004 or 2005-most
likely 2005
"Andy Kendall" <ak> wrote in message
news:ue**************@TK2MSFTNGP11.phx.gbl...

I too have this problem. I fill my spare time developing with digital
dashboard. It's so robust and useful. I simply can't understand how I ever
did without it. The problem is of course that it makes web app development
so quick and easy that I'm now getting my work done in half the time making that relase of 2004 all the more urgent.
"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....

[Art Vandelay]

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....