Visual Studio .Net

[n3il123]

Trying to run VS.Net on my PC (now its not a new I know) and it is just soooooo slow...

What spec machine do you guys that use it everyday have?

also does anyone have any recommendations on dual monitor setups? should I get 2 graphics cards or get one dual graphics card?

All input greatfully recieved

[ASB]

fwiw: P4M 1.7, 2GB Ram. It's fine. You really need at least 1gb ram IMO.

[VectraMan]

XP2100+, 768MB RAM. Anything of that order will be fine IMO. I put it on my 1Ghz 256MB laptop the other day and it was unbearably slow, mainly because of the RAM and the slow HDD. If it's thrashing the disk a lot, buy more RAM, and a faster disk can help a lot.

7 or 8 years ago I used to take a book into work as if you had to change something major in the code, there was nothing to do for an hour but sit and watch it rebuild. In those days it was worth investing in the fastest processors, lots of RAM and SCSI hard disks for development machines. These days any half decent PC that isn't too old is more than adequate.

Get a dual graphics card. Running two usually means one AGP and one PCI, and it's a bit hard to find PCI ones these days. I've got a dual output Radeon 9600 and 2x 17" LCD monitors. Two monitors makes such a difference when doing software development, I've been doing it for about 5 years.

[n3il123]

Cheers guys ... seems that Ram is king really then..

[DimPrawn]

Minimum of an 16 way Operon with 32MB of RAM should be okay until the next version comes out.

No seriously it's the RAM. Everyone seems to buy the latest and greatest CPU these days and think they can get away with 512MB of RAM, when Windows LOVES RAM.

I run 2GB and it's fine.

[Chappo]

ram, ram and more ram is what u need!

i went to a client to install vs.net, and the machine had 128mb ram - it took 4 1/2 hours to install, and then 20 odd mins before it would open up the initial project window screen...

I was happy as larry - getting paid £2.00 per minute to sit and watch this progress bar creeping across the screen!

I told them that they needed more ram, and that it wasnt feasable to install on this spec, but they wouldnt listen.

[NoddY]

ram, ram and more ram is what u need!

i went to a client to install vs.net, and the machine had 128mb ram - it took 4 1/2 hours to install, and then 20 odd mins before it would open up the initial project window screen...

I was happy as larry - getting paid £2.00 per minute to sit and watch this progress bar creeping across the screen!

I told them that they needed more ram, and that it wasnt feasable to install on this spec, but they wouldnt listen.

In UK plc mentality the next progression of this is to outsource your job; but I tell what exactly WON'T happen - they still won't go out and buy the fcuking RAM!

[DaveB]

I was happy as larry - getting paid £2.00 per minute to sit and watch this progress bar creeping across the screen!

I

£120 p/h? Bloody hell Chappo, who gets your contracts for you?

[mcquiggd]

I run VS 2003 and VS 2005 (not concurrently), on the same machine as Windows 2003 Enterprise Server, which is always running Exchange Server 2003, also SQL Server 2003 and SQL Server 2005 (which are not accessed concurrently, but are still in active), and often eMule or Azureous....

The system is running a single P4 at 3.8 Ghz.. has only an 800FSB (which is slow these days), 2 Gigs RAM, but... a 128 Meg caching raid controller with 10 x 10,000rpm SCSI drives in RAID and internal 10,000rpm IDE drives...

At work, VS2003, 1 gig ram, single 30 gig 7200 rpm HD, MSDE, 3.7 Ghz P4, and the slowest thing is the network to check stuff out of bloody Sourcesafe....

What ive found is that repeated stopping and starting in Debug mode causes the ASP.Net worker process to bloat in memory size... and also IIS. Killing the processes and simply doing an IISresest tends to cure it.

[Joe Black]

10 x 10,000rpm SCSI drives

Ehhh, the mind boggles...