I'm running a dual 3Ghz Xeon system (1MB cache per CPU) with 4GB RAM and two
10,000 rpm SATA drives and VS 2005 is incredibly slow -- frustratingly slow.
It is still this slow and still doesn't have the debugging capabilities of
VB6 from 5+ years ago. As you may have guessed, I'm very disappointed. I
also get many complaints from clients regarding the initial "slow" response
from any .NET 2.0 apps I've created -- many user wonder what is happening
and start clicking like crazy. Since a splash screen doesn't help for this
first initial run (framework getting initialized), nothing can be done for
the End User to "stay tuned and be patient" -- I really am shaking my head
and wondering what Planet Microsoft are on? Do they user will accept
this -- I wish, but in the real world, they don't and I'm asked to "fix it"
and coming back to them with "it ain't broke have patients" just does NOT
fly.
Please, someone just give me VB7, I'm over VS series of dog do.
Not all bad, VS 2005 does offer some nice features but those types of
features could have been implement in VB7 5 years ago.
But apparently Bill is worried about Google and their soon to be subscribed
online only Office suite -- oh brother, as if trading GB bandwidth (local PC
hardware level) for 1Mbps bandwidth (for those lucky minority -- and yes
high speed internet access is still in the minority) is something I want to
do or anyone else for that matter -- and I'm sure Ads and other such crap
will be tossed in. I truely feel Microsoft have gone off the deep end.
Rob.
"Julian" <ju****@kt88.freeserve.co.uk> wrote in message
news:%2***************@TK2MSFTNGP14.phx.gbl...
Hi
What in practice is required to run VS2005 pro?
I currently have a spare machine which is a Pentium 4 1.5Ghz 512Mb ram
XP 2 Home edition on which is just installed Team edition beta 2 , word
and photshop. VS just crawls on this and I wondered if this was typical
of the release version of pro as well and a daster machine is required?
Many thanks
Julian
