Hello everyone! I was programming in C++ using Visual Studio 6.0, I liked it because it does not crate tons of files and your project folder stays “clean”. After a while some of the guys told me that I should use Visual Studio 2005 or higher as it is a newer standard. That made me think, if I am not a pro developer at the moment, and I am working mostly on my 2D Graphics engine, and doing some experimentation with matrices and vectors and overall engine structure and design.
So the question is: Is there any serious reason why I should not use VS 6.0 anymore and switch to newer one? Ken, why VC 6.0 C++ is still your IDE/Compiler of choce? (if it still is)
1. std::string multicore/proc issues in the runtime, re: KB813810 http://support.microsoft.com/kb/813810 2. poor STL support 3. even poorer Standard C++ support -by user D.Shawley
But then. If it works for you and for the people you share your programs with... Why switch?
You could try Code::Blocks or Programmers Notepad and combine them with the free Microsoft C++ compiler. Then, you would have to create makefiles and all those irritating details yourself :/ At least for PNotepad.
Annihilator at
Good link! But as far as i remember Ken still uses VS 6.0 C++ Ken, are you?
Jinroh at
Not that anybody really cares what I use, but personally I use VS6.0 still.
At work I use VS 2003 and I really like it, the CTRL-K shortcut is really nice for auto-indenting your code. ^o^ It saves me a lot of spaces since some of my Co-Workers have different style, and well, style police. :P
It's really nice for C++ oriented stuff is what we do for our projects at work. For my personal projects, well, my first job was an embedded C programmer and I have that style in my personal projects. So, I don't usually code C++ so it works fine for me to use VS6.0. Though with all of the convenient C++ libs that we use at work that may change, but I'm just still stuck in the ARM9 C mode from my first real coding job.
Though the real reason may just be the fact that my 2003/2005 disks are at my parents in a box somewhere. :P
TX at
I code EDuke32 in VS2008 with an extension called Visual Assist X, it makes for a pretty awesome IDE. Can't really stand VS without VAX anymore. I don't use Microsoft's compiler, however.
Awesoken at
Yes, I still use MSVC 6.0, although I only use the compiler. For the IDE, I use KC.EXE, a small text editor with a key (F5) to automate compiling (i.e. save->compile->link->run).
I use MSVC 6.0 mainly because I can create much smaller EXE's with it. MSCVRT.DLL has been included with all versions of Windows since Win98, so it is safe to use the /MD option without complaints of a missing DLL. I have tested later versions of MSVC, but I have yet to see a noticable improvement in speed, or a bug fix that affects me.
Stroggos at
Personally I use MinGW and Code::Blocks. They are both fast and reliable I i'll stand by them! Every now and again I will use MSVC++ 2008 Express. Because it makes fast and small executables. But 90% of the time I use MinGW and CodeBlocks
yunharla at
i wont recommand vs 2005 scince it is a constant pain-in-the-.... elbow :P vs 6.0 and 2003 seemed nice to me but i didnt worked much withem scince i prefer mingw/devcpp
Batmanifestdestiny at
Stroggos said at
Personally I use MinGW and Code::Blocks. They are both fast and reliable I i'll stand by them! Every now and again I will use MSVC++ 2008 Express. Because it makes fast and small executables. But 90% of the time I use MinGW and CodeBlocks
I also use MinGW and Code::Blocks. My only issue with it is that I can't seem to figure out where to put openGL files to use the library.
CaimX86 at
I always thinking I was late... but look that, there are many guys using MS 6.0 compiler.