1

The process of compiling, creating exe and running it is very slow on my machine(and also stopping the exe by the stop button). Its a windows forms app with a very simple form. I see that in Release mode it works faster, but not fast enough.

There is also slow down of IDE right after I hit the stop button, it really needs to think about something for at least 10seconds(I understand that I'm killing the app, but why VS cant just understand it and don't think about it?).

Maybe uninstalling something or disabling something?

P.S. This is slow only after a few runs, but I think I just got too old machine. I would rather not update it right now.

I have 2GB of RAM.

abatishchev
  • 98,240
  • 88
  • 296
  • 433
IAdapter
  • 62,595
  • 73
  • 179
  • 242

4 Answers4

7

I think the accepted solution is to upgrade to VS 2008.

David Heffernan
  • 601,492
  • 42
  • 1,072
  • 1,490
  • 1
    I have the same problem as the OP. My computer is quite old (6 years) and VS2008 is a huge "upgrade" compared to VS2010. – Marlon Feb 06 '11 at 19:15
  • 2
    @IAdapter No, I meant *upgrade* to VS 2008! Seriously, VS 2008 is known to be quite a lot faster, lots of people have had trouble with 2010 performance. 2010 was a significant re-write, 2008 is super stable and polished. – David Heffernan Feb 06 '11 at 19:16
  • This sage advice to 'upgrade' to a previous version of something has been around for ever, and is given about every new version of every popular bit of software. It says much more about the innate conservatism of human beings than it does about development environments... – Will Dean Feb 06 '11 at 20:50
  • @will 2010 will get better over time just as xp did and just as vista did through service packs. Personally I'm happy with 2010 but 2008 is faster and if it does what you need why not wait? – David Heffernan Feb 06 '11 at 20:54
5

Release mode will make the compiler slower, if anything. It generally makes the finished application smaller/faster, though.

VS2010 needs an enormous amount of memory, and if you have less than 3-4G, you're almost certainly being hit by that - that might be a cheaper upgrade than a new machine.

But all versions of the 'Visual' dev tools, right back to VC1.0, have been beasts that have required reasonably up-to-date computer specifications. I'm afraid that's just the way things are.

Will Dean
  • 39,055
  • 11
  • 90
  • 118
  • I have 2GB, thx for answer. Now I know what I need to upgrade :) – IAdapter Feb 06 '11 at 19:16
  • Interestingly, even on 4 GB some of my computers had some trouble. I recently added more memory to my desktop (which had 4 GB to start with) and VS2010 got noticeably faster. – Mike Bailey Feb 06 '11 at 19:52
  • @Mike - I concluded VS2010+R# was unusable for WPF development on a 32-bit OS, and so went to an 8G/64-bit machine to avoid the endless virtual memory problems - I definitely agree that 4G is not a sure fix. – Will Dean Feb 06 '11 at 20:48
2

The BETA service pack worked wonders for me - lots of bits of VS2010 that were broken (like macros) started working and its significantly faster for me now - ymmv tho :)

Microsoft VS2010 SP1 Beta Link

Tollo
  • 505
  • 4
  • 14
0

This is a duplicate question, but I can't find the duplicate. So in summary here's what the other one said :)

1) Get more memory, 4gig as a minimum.

2) Disable extensions

3) A list of changes to speed things up 1

4) Might of found the original

I love all my extensions, so memory is key to me.

Community
  • 1
  • 1
Ian
  • 4,885
  • 4
  • 43
  • 65
  • I have a similar question at http://stackoverflow.com/questions/3054504/visual-studio-2010-how-to-reduce-its-memory-footprint – GregC Apr 07 '11 at 10:13