Which VS do you like?
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
I can only speak for C++ (desktop and embedded) -- VS2008... Crashes much less often than 2005 (which crashed almost once per hour, more often when adding classes = the usual suspect: Intelisense...). The debugger for VM5/6 are much faster in 2008 than in 2005 (relatively speaking of course -- it's not fast for any definition of the word). I recommend a fast machine (fast cpu, 2GB+ and fast harddiscs) and Whole Tomatoes "Visual Assist X". It makes a big difference...
-
Which Anonymous font, their are loads of 'em.
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
VS 2008 works well. Intellisense is kind of broken for C++ though. It works 75% of the time (which is better than the 1% I got from VS 2005).
-
Which Anonymous font, their are loads of 'em.
-
Mark Simonson one. Google hit #1. http://www.ms-studio.com/FontSales/anonymous.html#[^]
Thanks, looks great in the ide.
-
Based on one of your articles I assume you are coding in C++ and MFC. Unfortunately for me as a MFC programmer, new versions of VS were all nightmare. At least 'Express' editions. If you are going to continue MFC, then please consider these: -You'll not have "class wizard" any longer. -The IDE is too much slower because of it's intellisense. Please don't ignore this specially if your CPU has 1 core. -Sometimes IDE crashes for no good reason: eg. In VS2008 try adding a class based on CRecordset, then select a dynamic connection to an odbc source, I bet it will crash. -Old codes will not work often. Due to changes to the compiler, most old codes have errors now. This is not such a big problem, unless in one of your project you use a liberary that has compatibility issues(which I believe many libs have) and there's not a new version available. -I was not able to find "Add window message handler" dialog. -etc.(There are a lot more) As an MFC programmer, I'm sometimes stocked in situations that I decide to leave MFC forever, then I remember steve balmer saying developers and think it will be sure solved?! For older versions, I cannot add new(?) SDKs(All sort of errors). If a library needs it, I have to use new versions of IDE where I face new problems. I sometimes choose another way: I code in VS6 and compile in new VS! better way is to create a batch file that calls new compiler so no need to the new IDE at all.
// "In the end it's a little boy expressing himself." Yanni while (I_am_alive)
{
cout<<"I love to do more than just programming.";
}Clearly VC6 - one of the few things MS has done that worked ...... As MFC/SDK developers moving to VS2005 (don't even think about 2002/2003!) - lot of work converting code and runtime problems due to exceptions being thrown from legacy code. Very frustrating having to re-write/correct but in heart of hearts know the code is now better..... Unfortunately VS2005 builds are really irritating as something in the dependencies is broken and too easy to have to rebuild everything (hint get rid of the solution build button!). For .net then 2008 or 2005 is fine - but .net is for wimps anyway :) Oh didn’t mention - expect VS to crash on regular basis – but you knew that anyway. Bob PS why does Microsoft insist on adding features to products rather than making them work correctly (how many people will use 3.5 features and how many would like an IDE that doesn’t crash…
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
I can't think of any advantage migrating step by step after VS7 ie if I were on VS7 I'd skip VS8 and go straight onto VS9 - its backward compatibility feature, via specifying which .NET is to be targeted makes it a no brainer. Not sure about going from VS6 straight into VS9, being a conservative I'd consider going to VS7(2003) as an stepping stone to VS9(2008), my experience with VS6 is limited and very rusty.
TUT
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
I use VS 2005 for C++ development and am very happy with it apart from the occasional hang in the debugger which requires you to kill it and start all over again. I would switch to VS 2008 if it weren't for the fact that Edit-and-Continue (surely the pearl in ths shell) doesn't report compiler errors (!!). Does anyone know if this is fixed in SP1 beta, by the way? If so, I will have another go, but I don't want to go through all that hassle only to find I have to go back to VS 2005 again. And another thing: why is the Performance Analyser not included in the Professional edition???? Surely all professionals need to profile their code. Grrrrrrrrrrrrr.
Paul Sanders http://www.alpinesoft.co.uk
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
2008 is clearly the most complete and stable in my experience. i have used every version since vs6. still have to go back to vs2003 every once in a while, reminds me how far it has come since.
---Guy H ;-)---
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
VS 2008 is by far the best version to date for so many reasons. Only downsize is its large footprint . I run it on a MAC running VISTA under VMWARE FUSION so it can be a bit slow to load large projects with lots of pages but its built in features and great support for third party enhancements make it a winner.:cool:
When prediction serves as polemic, it nearly always fails. Our prefrontal lobes can probe the future only when they aren’t leashed by dogma. The worst enemy of agile anticipation is our human propensity for comfy self-delusion. David Brin Buddha Dave
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
For C++ I prefer (and still use) VS6. The versions after that are sluggish, probably because of .NET. I've seen benchmarks that show C++ in VS6 produces significantly faster executables than the later versions. I like the simple style of VS6; it lets me get where I want and doesn't get in the way.
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
My hobby-programmer experience: Forget MFC, WTL is much more fun:) , and save some money until the Next Big Thing (hopefully, the version which will be the vc6 killer - as I read from the posts) by using VC2005 (2008?) Express+Platform SDK 2003 R2 + ResEdit + ToolbarEditor - with this combo you can't lose.
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
I went directly from VC6 to VS2005. It took some time to get used to, but I'm happy with it. I haven't heard much of anything bad about VS2008 though, and in your position I'd probably go that route if you're still relatively early in your development cycle. - VC6 was snappy, but most everything in VS2005 is notably slower. Leaves me with a feeling like I'm repairing watches while wearing welding gloves. I've heard VS2008 is a bit peppier, but FTM I have to stick with VS2005. - VS2005 conforms more closely to the C++ standard than VC6. VC6 code will may have to be modified (corrected) to compile under VS2005. - The STL code in VS2005 is a bit more pleasing to look at than in VC6. - In VS2005 you loose the class wizard (You. can. add. variables. via. the. gui., but. only. one. at. a. time.). - When compiling my legacy apps I typically get a plethora of deprecated/security warnings. Ugh. - For those that care, VS2005 brief emulation isn't all that hot.
-
Clearly VC6 - one of the few things MS has done that worked ...... As MFC/SDK developers moving to VS2005 (don't even think about 2002/2003!) - lot of work converting code and runtime problems due to exceptions being thrown from legacy code. Very frustrating having to re-write/correct but in heart of hearts know the code is now better..... Unfortunately VS2005 builds are really irritating as something in the dependencies is broken and too easy to have to rebuild everything (hint get rid of the solution build button!). For .net then 2008 or 2005 is fine - but .net is for wimps anyway :) Oh didn’t mention - expect VS to crash on regular basis – but you knew that anyway. Bob PS why does Microsoft insist on adding features to products rather than making them work correctly (how many people will use 3.5 features and how many would like an IDE that doesn’t crash…
Bob1000 wrote:
For .net then 2008 or 2005 is fine - but .net is for wimps anyway
Ah, but you plan to be around forever to maintain your software in C++, or don't care that you'll be leaving an Aston-Martin in the hands of a high-school mechanics student. .NET is for building Model T's (or, for that matter, F-350s) that anyone can fix. I can say that, I began my pro life writing K&R C on DOS 3.1 (where an exception was only an exception if it noticeably did something, which usually required a power-off or the lil red reset button). It's the same story for Java. Choosing sandbox computing in this day and age is smart, because there's too much code and not enough debuggers with the talent and endurance to find subtle native environment errors (it's difficult enough to find those with the talent and endurance to debug subtle sandbox environment errors). Luckily, there's always gonna be room for the C++ tweaker :)
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
Thanks everyone for your input. It looks like VS2008 is the way to go. And yes we will be porting an MFC+FORTRAN app, with all the problems that may entail (as some of you have kindly highlighted). That said, we'll have to switch FORTRAN compilers too, so it is never going to be a trivial task (hopefully not too difficult, but not trivially easy either).
-
We are still using VS6 (ahh...FORTRAN integration.....), but at some point we'll have to make the leap to a newer IDE. Is there a concensus as to which flavour is better? Or should we just go to the newest (and best ? haha!)
Victoria's Secret :cool:
-
Once you have VS2002, I used to think it didn't matter, but I am quite partial to the two I use, 2005 and 2008. I notice the UI is prettier when I have to go back, and I see nothing that's gotten worse with time. Not in .NET anyhow. C++ support is anotehr thing.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
Christian Graus wrote:
I see nothing that's gotten worse with time.
Overall each new IDE is better. However, there were IMO some usability regressions from 2003 to 2005. Not used 2008 apart from C# Express and then that only briefly.
Kevin