views:

68

answers:

5

(Hope to be non OT) Hi, i'm a little exasperated about running vs.net 2008 on an acer aspire with an intel t2350. I know, this hardware is not the "last" and the best we can find on the market. So i'm thinking to buy a new notebook. For your experience, which type of processor i can buy ? I found, here in italy, acer notebook between 350-500 euros with t4400 and 2-3 gb ram. Is it enough to have a good "working experience" with vs (with good i intend not to wait 10-20 seconds when i switch from asp.net design to asp.net source code) ?

Any answer is appreciated

+1  A: 

I think this belongs in SuperUser forum.

Here are the minumum requirements for:

VS 2010

VS 2008:

Computer with a 1.6 GHz or faster processor Visual Studio 2008 can be installed on the following operating systems: Windows Vista® (x86 & x64) - all editions except Starter Edition Windows® XP (x86 & x64) with Service Pack 2 or later - all editions except Starter Edition Windows Server® 2003 (x86 & x64) with Service Pack 1 or later (all editions) Windows Server 2003 R2 (x86 and x64) or later (all editions) 384 MB of RAM or more (768 MB of RAM or more for Windows Vista) 2.2 GB of available hard-disk space 5400 RPM hard drive

VoodooChild
A: 

If you're developing with less than 4gb and a 64 bit OS you're living in 1996.

64bit, 4gb of memory.

Will
Dunno what that is in euros, but that's a 6-800 buck laptop nowadays.
Will
I am using a 64-bit but honestly I don't know if it really makes a difference. In your opinion particularly where do you see the performance boost.
VoodooChild
I'm living in 1996
Matias
If you're developing with less than 4 *MB* you're living sometime LONG before '96...
antik
@voodoo 64 bit doesn't give you a performance boost; it allows you to actually access all 4gb of memory address space. There's no point in having 4gb of physical memory on a 32bit machine because the OS has to reserve some of that address space for hardware. Its all about the memory. Understand?
Will
+1  A: 

I think it relies in the weight of the solution you're working on. Switching from asp design to source code is really slow. Personally, I had bad experiences and I don not find productive using the design view. I used VS2008 in machines with a really good hardware configuration and this 'switching' still slow, it must be a bug.

In this link you can find the 'official' info that you're looking for.

Also I found that there was an effort to reduce that loading time, but in my opinion, is not enough.

Matias
thank you. Your link are very useful. Now i know this is not (almost) a problem regarding my machine...
stighy
+1  A: 

Just about any machine with 2GB of RAM will run the actual Visual Studio editor just fine.

However, development systems rarely stop at just a single editor. You might typically have two or three instances of the editor, plus a web browser or two, a task management system, a web server and a database engine, and maybe an additional VM or two. Not to mention power left over to actually run, debug, and compile the app you're working on.

Because the load here is typically spread over several apps/processes, a development machine can generally make pretty good use of a quad code processor with at least 4GB of RAM.

Joel Coehoorn
A: 

I find using a Solid State hard drive do alot for the performance. That and 4gb of ram and a decent CPU and you a good to go!

Johan Wikström