Which VS do you like?
-
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 :)
[ah, but you plan to be around forever] Hoping to be ! [to maintain your software in c++] No to be around on a large yacht in the Caribbean! Think there are still a fair number of C++ software engineers out there and there will be for the foreseeable future, if for no other reason .net just can't hack it in the realtime arena (which is fair enough as its not designed to be!) - Horses for courses as they say. As a replacement for Visual basic its great....plus some
-
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 :)
Hoping to be ! No to be around on a large yacht in the Caribbean! Think there are still a fair number of C++ software engineers out there and there will be for the foreseeable future, if for no other reason .net just can't hack it in the realtime arena (which is fair enough as its not designed to be!) - Horses for courses as they say. As a replacement for Visual basic its great....plus some
-
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
[And another thing: why is the Performance Analyser not included in the Professional edition???? Surely all professionals need to profile their code. Grrrrrrrrrrrrr. ] Agree - dumb is the word as are the other missing professional features. Do miss VC6 life was a lot easier then....!
-
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.
-
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've developed professionally with MS products since VB4, and I've had every version of VS since then (tho I have yet to try VS2008). To tell you the truth, I've actually come to love the Express Editions of VS2005. I have access to the full-blown edition, but for some reason I prefer to use the Express editions. I've written a number of production applications with it with no problem. :laugh:
-
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.";
}Hamed Mosavi wrote:
The IDE is too much slower because of it's intellisense.
Visual AssistX[^] solves that one. Not the 1-core thing though ;)
"impossible" is just an opinion.
-
Do you know if Oz has any plans to apply the same or similar treatment to the current VS IDEs?
Kevin
-
Yeah, I seem to remember that but thought he may have changed his mind. Trouble is VC++ 6 is a dead product now.
Kevin
-
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!)
-
VS2008 Pro, but then I rarely do anything but C# stuff any more. Better performance than VS2005 and handles all the new stuff like LINQ etc, less susceptible to designer crashes as well. I wouldn't know about C++ support though because I only use the very basics of that (well usually not even C++, just plain ol' C).
I doubt it. If it isn't intuitive then we need to fix it. - Chris Maunder
Yes, I use VS2008 and new features too :-D In the past I use VC++ 6 Std, currently box of it stand on my shelf ;P
---------------------------------------------- When the sorrow takes me I'm embracing the darkness alone Please - take me home [Embraced By Darkness - Saturnus]
modified on Monday, June 16, 2008 5:13 AM
-
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!)
don't know. last time i was useing VS5. so far i had no reason to use VS 6, except for VC++ 6, but didn't like it.