Visual Studio .Net

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

DaveB replied

1 March 2006, 22:05
Originally posted by mcquiggd

Two external SCSI enclosures... makes one hell of a difference....

Noisy as feck when they are on though.

Keeps the heating bills down though I would imagine.....
Leave a comment:
mcquiggd replied

1 March 2006, 22:01
Two external SCSI enclosures... makes one hell of a difference....

Noisy as feck when they are on though.
Leave a comment:
Joe Black replied

1 March 2006, 21:13
Originally posted by mcquiggd

10 x 10,000rpm SCSI drives

Ehhh, the mind boggles...
Leave a comment:
mcquiggd replied

28 February 2006, 23:35
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.
Leave a comment:
DaveB replied

21 February 2006, 13:20
Originally posted by Chappo

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?
Leave a comment:
NoddY replied

20 February 2006, 14:39
Originally posted by 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.

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!
Leave a comment:
Chappo replied

19 February 2006, 10:58
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.
Leave a comment:
DimPrawn replied

18 February 2006, 18:11
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.
Leave a comment:
n3il123 replied

18 February 2006, 14:45
Cheers guys ... seems that Ram is king really then..
Leave a comment:
VectraMan replied

18 February 2006, 14:34
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.

Last edited by VectraMan; 18 February 2006, 14:39.
Leave a comment:
ASB replied

18 February 2006, 12:46
fwiw: P4M 1.7, 2GB Ram. It's fine. You really need at least 1gb ram IMO.
Leave a comment:
n3il123 started a topic Visual Studio .Net

18 February 2006, 11:57
Visual Studio .Net

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
Tags: None