I've seen a couple of times people in this community recommending VS 2010 or sticking to 2008. I'm currently using 2008 but will consider an upgrade..

The only thing I don't like about 2008 is the broken autocomplete, did they fix that?

What are peoples opinions on the upgrade/ reasons why they don't want to upgrade? e.g. fast, slow, buggy, good features

Never used 2008, only used 2010. Yes autocomplete works in 2010

Well i am from the Qbasic age... so i don't really care about the fancy GUI in 2010...

So my vote goes to vs2008

Hmmm. I'll give it a test then; hope its not too bloated.

I prefer Visual 2008, because i'm used to it and it's reccomended by Esenthel Engine I don't need Visual for another things.

The intellisense improvements are really great. The GUI is good but the intellisense is my big plus PRO

for me vs2010 runs slower, so I stick to vs2008

I completely uninstalled 2008 & all components, then installed visual studio 2010 express and have been using it for the past 4 hours or so. First thing I had to deal with were a lot of problems converting the project, and finding where to change project settings etc. Eventually I converted the "Tutorials.vcproj", but only made it survive the XML conversion parse errors by deleting 4 configurations directly from the .vcproj (every configuration with a x64 build in) in notepad++ (luckily their broken parse system tells you which line of the file the error is on). I agree with Esenthel, it's much slower to startup and has quite a lot of background processing which I find very annoying. But yes, the autocomplete seems to be fixed. Not sure whether to convert the other computers now..

EDIT: Also for some reason the "output directory" needs to be shortened "for all configurations" (following conversions) to just "$(SolutionDir)" - example of something which converts is: http://www.cwkx.com/storage/Tutorials.vcproj

I just have to ask, whats broken with autocomplete in vs2008?

The intellisense database gets corrupted every now and then; it eventually fixes itself but the only immediate solution is to delete .ncb and restart VS (w/o writing macros). But if there's a fix for this, i'd definitely not consider 2010.

c++ macro

Could this help you? 4'th post.

Well i use VAssistX to fix that intelli problem in vs2008

Thanks; I saw the macro solution but VC++ 2008 express didn't support them (I didn't wanna install all the other MS stuff either), also VAssistX doesn't support VC++ 2008 (express) -right? I thought it only supported pro. +$99 for a license.. Hmmm stil can't decide which is best, i'm noticing the speed a little less now, maybe i'm getting used to it.

2010 + VAssistX Esenthel works on 2010 very well. It looks nice, I can't explain why. Probably it's color style and great extension manager.
I use 2008 too, but it's more difficult to use for me (I dont know why). And VAssistX doesn't work on it :( (installer is for all versions but I found only VS2010-Extension file and it works only for 2010).
I use 2*2 (2x2) versions of visual studio. 2x2 = 2(2008+2010)*(express+professional).

Conversion is not a problem for me. I know what to change to project work.

Speed was pretty noticable the first few times I used it, but now on a cold start it starts in 1-2 seconds though I'm pretty sure this is because of SuperFetch. Builds take 2-3 seconds, Rebuilds take 10 seconds but this is all dependent on your project size.