VS 6.0 vs VS 2005 (c++)
-
I was thinking about switching from vs 6.0 to 2005 althought I don't have any good reason. But after I've tried vs 2005 I'm really disappointed. 1. IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class). 2. compiling is also insanely slow. I know I don't have too fast computer (Athlon 1800+, 7200 rpm hdd @ WinXP SP2) but when I compare it to vs 6.0, it is bad : MFC project (created in 6.0 and imported to 2005 for testing), release biuld with static MFC (all intermediate files deleted before compiling): - VS 6.0 with 512MB RAM : comple time 1:58 (mm:ss) - VS 6.0 with 1GB RAM : 1:45 - VS 2005 , 512MB RAM : 5:26 - VS 2005, 1GB RAM : 4:11 I've noticed that new VS is building browse info too and I cannot turn it off althought I don't need it so it added maybe up to 40-60 secs to compile - but it's not my problem :~ Have anybody else the same experience ? For me nicer icons are definitely not worth to decrease my productivity :(
rrrado
welcome to the world of software improvements. Compair the speed of windows 3.1 with XP on the same computer to get the idea. (if you could find a computer that would run both:omg:)
-
Fernando A. Gomez F. wrote:
What about this: Visual C++ 6 was released before the C++ standard was approved. Visual C++ 7/7.1/8 already incorporates many features of the standard.
well for MFC app standards are not important, I won't compile it for linux even with standardized compiler. so huge compile slowdown cannot be explained by better standards :(
rrrado
rrrado wrote:
so huge compile slowdown cannot be explained by better standards
turn off optimization.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
I was thinking about switching from vs 6.0 to 2005 althought I don't have any good reason. But after I've tried vs 2005 I'm really disappointed. 1. IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class). 2. compiling is also insanely slow. I know I don't have too fast computer (Athlon 1800+, 7200 rpm hdd @ WinXP SP2) but when I compare it to vs 6.0, it is bad : MFC project (created in 6.0 and imported to 2005 for testing), release biuld with static MFC (all intermediate files deleted before compiling): - VS 6.0 with 512MB RAM : comple time 1:58 (mm:ss) - VS 6.0 with 1GB RAM : 1:45 - VS 2005 , 512MB RAM : 5:26 - VS 2005, 1GB RAM : 4:11 I've noticed that new VS is building browse info too and I cannot turn it off althought I don't need it so it added maybe up to 40-60 secs to compile - but it's not my problem :~ Have anybody else the same experience ? For me nicer icons are definitely not worth to decrease my productivity :(
rrrado
rrrado wrote:
Have anybody else the same experience ?
You don't hang out much here do you? :-D Anyway, VC++ 2005 has a much better compiler, both in terms of language support and optimizations (google for NRVO, for instance), usable C++ Standard Library (but watch for checked iterators[^] in the release mode), and the much improved debugger and call browser. On the flip side the new IDE it is all but unusable for MFC development, so if that is your main line of work, better stick to VC6.
-
You are not, in fact, the only person that prefers VC6. Check out here[^] for a long list of complaints about VC7.x. If VC6 does what you need, why change? Especially when the thing you'd be changing to is an inferior product.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Hungarian notation FTW
Michael Dunn wrote:
You are not, in fact, the only person that prefers VC6. Check out here[^] for a long list of complaints about VC7.x. If VC6 does what you need, why change? Especially when the thing you'd be changing to is an inferior product.
Sad thing is that vs 6.0 is not sold anymore. I'm going to start project with new company so I'll have to check out if it is acceptable to purchase VS 2005 and "downgrade" it to 6.0. I know that some microsoft's licenses allowed downgrading but I don't now if it is allowed for this case.
rrrado
-
rrrado wrote:
Have anybody else the same experience ?
You don't hang out much here do you? :-D Anyway, VC++ 2005 has a much better compiler, both in terms of language support and optimizations (google for NRVO, for instance), usable C++ Standard Library (but watch for checked iterators[^] in the release mode), and the much improved debugger and call browser. On the flip side the new IDE it is all but unusable for MFC development, so if that is your main line of work, better stick to VC6.
-
I was thinking about switching from vs 6.0 to 2005 althought I don't have any good reason. But after I've tried vs 2005 I'm really disappointed. 1. IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class). 2. compiling is also insanely slow. I know I don't have too fast computer (Athlon 1800+, 7200 rpm hdd @ WinXP SP2) but when I compare it to vs 6.0, it is bad : MFC project (created in 6.0 and imported to 2005 for testing), release biuld with static MFC (all intermediate files deleted before compiling): - VS 6.0 with 512MB RAM : comple time 1:58 (mm:ss) - VS 6.0 with 1GB RAM : 1:45 - VS 2005 , 512MB RAM : 5:26 - VS 2005, 1GB RAM : 4:11 I've noticed that new VS is building browse info too and I cannot turn it off althought I don't need it so it added maybe up to 40-60 secs to compile - but it's not my problem :~ Have anybody else the same experience ? For me nicer icons are definitely not worth to decrease my productivity :(
rrrado
I'd say your lucky if the compile time is only 4-5 minutes. The main solution I have to build used to take about 5 minutes in VC6, now takes over 45 in VC2005. I still have to use VC 6 for some things and I still prefer it to VC 2005 as far as the IDE is concerned. The compiler in VC6 is faster, the IDE is better for C++ and with Visual Assist from Whole Tomato Software, VC6 is the hands-down winner for basic C++ development. However, the compiler in VC6 is far from standards compliant, you cannot use any .NET/managed components without lots of hacking (which you have to do in VC 2005 anyway), both blow up sometimes, etc. At the end of thd day, I made the switch so that I could use more standard compliant C++, take advantage of managed code where needed (huge caveat there though), and have one IDE for C++ and ASP.NET. The transition has not been painless and I would say that my development PC was adequate for VC6, but not for VC 2005. In fact, my new development PC should arrive tomorrow (Quad Core, WinXP 64, 2gb, 160gb RAID, dual monitor support, etc). Hopefully that will be enough to make life with VC 2005 smooth enough. Oh yea, don't even think about using the /clr option with an MFC extension DLL. The compile time is enough to make you want to scream. Find an alternative.
-
I was thinking about switching from vs 6.0 to 2005 althought I don't have any good reason. But after I've tried vs 2005 I'm really disappointed. 1. IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class). 2. compiling is also insanely slow. I know I don't have too fast computer (Athlon 1800+, 7200 rpm hdd @ WinXP SP2) but when I compare it to vs 6.0, it is bad : MFC project (created in 6.0 and imported to 2005 for testing), release biuld with static MFC (all intermediate files deleted before compiling): - VS 6.0 with 512MB RAM : comple time 1:58 (mm:ss) - VS 6.0 with 1GB RAM : 1:45 - VS 2005 , 512MB RAM : 5:26 - VS 2005, 1GB RAM : 4:11 I've noticed that new VS is building browse info too and I cannot turn it off althought I don't need it so it added maybe up to 40-60 secs to compile - but it's not my problem :~ Have anybody else the same experience ? For me nicer icons are definitely not worth to decrease my productivity :(
rrrado
rrrado wrote:
Have anybody else the same experience ?
Most folks have been saying this since it first came out. That's about three years of "Man this new compiler is slow" comments.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
-
I was thinking about switching from vs 6.0 to 2005 althought I don't have any good reason. But after I've tried vs 2005 I'm really disappointed. 1. IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class). 2. compiling is also insanely slow. I know I don't have too fast computer (Athlon 1800+, 7200 rpm hdd @ WinXP SP2) but when I compare it to vs 6.0, it is bad : MFC project (created in 6.0 and imported to 2005 for testing), release biuld with static MFC (all intermediate files deleted before compiling): - VS 6.0 with 512MB RAM : comple time 1:58 (mm:ss) - VS 6.0 with 1GB RAM : 1:45 - VS 2005 , 512MB RAM : 5:26 - VS 2005, 1GB RAM : 4:11 I've noticed that new VS is building browse info too and I cannot turn it off althought I don't need it so it added maybe up to 40-60 secs to compile - but it's not my problem :~ Have anybody else the same experience ? For me nicer icons are definitely not worth to decrease my productivity :(
rrrado
I thought of one more thing I really like about the IDE in VS2005. If you and a mutltiple core machine, the IDE will compile multiple projects simultaneously as long as they are not dependant on each other. I have one system that has 20 components. A quad core machine rips through that in no time. Multiple cores are wasted on VS6.
-
Michael Dunn wrote:
You are not, in fact, the only person that prefers VC6. Check out here[^] for a long list of complaints about VC7.x. If VC6 does what you need, why change? Especially when the thing you'd be changing to is an inferior product.
Sad thing is that vs 6.0 is not sold anymore. I'm going to start project with new company so I'll have to check out if it is acceptable to purchase VS 2005 and "downgrade" it to 6.0. I know that some microsoft's licenses allowed downgrading but I don't now if it is allowed for this case.
rrrado
Another possible way to get VS6 is through a subscription to MSDN. That's quite expensive, but last time I checked, you could still get old products like VS6 if you're a subscriber. Also, as you've seen in this thread, some people seem to like the newer VSs better. Maybe somebody somewhere who no longer uses VS6 might have their copy for sale. (No I don't. I don't have an installation CD for it either. Wish I did.) BDF
-
I was thinking about switching from vs 6.0 to 2005 althought I don't have any good reason. But after I've tried vs 2005 I'm really disappointed. 1. IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class). 2. compiling is also insanely slow. I know I don't have too fast computer (Athlon 1800+, 7200 rpm hdd @ WinXP SP2) but when I compare it to vs 6.0, it is bad : MFC project (created in 6.0 and imported to 2005 for testing), release biuld with static MFC (all intermediate files deleted before compiling): - VS 6.0 with 512MB RAM : comple time 1:58 (mm:ss) - VS 6.0 with 1GB RAM : 1:45 - VS 2005 , 512MB RAM : 5:26 - VS 2005, 1GB RAM : 4:11 I've noticed that new VS is building browse info too and I cannot turn it off althought I don't need it so it added maybe up to 40-60 secs to compile - but it's not my problem :~ Have anybody else the same experience ? For me nicer icons are definitely not worth to decrease my productivity :(
rrrado
rrrado wrote:
IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class).
I've had the opposite experience - Class View and Intellisense both were usually broken for me using VS6, especially when dealing with templates. The whole "browse info" thing felt tacked on and wasn't worth the additional build time - VS2005's ability to navigate through large class structures without an explicit build step has been very useful.
rrrado wrote:
2. compiling is also insanely slow.
Make sure you have plenty of memory, and have configured pre-compiled headers properly - on one project, I saw compile times drop from nearly an hour before configuring PCH to just under 20 minutes - only slightly longer than in VC6. Frankly, the improvements to the compiler and standard libraries were worth it for me - and the debugger is so much better it's not even funny; i used the VS2005 debugger for close to a year before moving to VS2005 for builds. The IDE itself has some issues, but frankly it's a half-decent text editor - i can live without the wizards.
every night, i kneel at the foot of my bed and thank the Great Overseeing Politicians for protecting my freedoms by reducing their number, as if they were deer in a state park. -- Chris Losinger, Online Poker Players?
-
I thought of one more thing I really like about the IDE in VS2005. If you and a mutltiple core machine, the IDE will compile multiple projects simultaneously as long as they are not dependant on each other. I have one system that has 20 components. A quad core machine rips through that in no time. Multiple cores are wasted on VS6.
Paul Watt wrote:
Multiple cores are wasted on VS6.
no way! something's gotta be running iTunes and FireFox while VC6 builds. i vote the other core gets it.
Paul Watt wrote:
If you and a mutltiple core machine, the IDE will compile multiple projects simultaneously as long as they are not dependant on each other.
it's fun to watch the performance monitor while VS05 is chugging away. sometimes it'll hit 100% and sit there, then drop down to a solid 50%, when it hits something it can't do in parallel.
-
rrrado wrote:
Have anybody else the same experience ?
yes. it's really a drag doing any MFC UI work with the VS05 IDE. the "class wizard" stuff from VC6 has been split up and scattered all around the IDE (if not thrown-out entirely). the resource editor is a pain. etc.
Chris Losinger wrote:
the resource editor is a pain. etc.
It started to suck real bad in VS.NET 2k3, which is one of the reason why I do much resource editing directly in the .rc file these days. Feels like a step backwards... :~
-- Raaaaaaaaaaaaaaaaaaaaa!
-
welcome to the world of software improvements. Compair the speed of windows 3.1 with XP on the same computer to get the idea. (if you could find a computer that would run both:omg:)
hlmechanic wrote:
welcome to the world of software improvements
It's different actually. VS 6.0 is more quick but is not like Win3.1 compared to win95. Considering the fact that he is going to do MFC, I believe it's just the opposite. It's not that "it's a bit slower", It's so damn slow that I had to search the web and learn how to rename or remove a file and disable intellisense totally, to be able to work. Even this job did not solved all performance problems. Don't believe it, Try to add some member variable or functions to see what is real pain. And my machine is not quick, but not that slow: An Intel p4 2.4(1MB L2 cache), 2HDD both 7200rpm sata 80GB and 300GB(8MB buffer), 1GB of ram and my os was xp sp2. Then comes the most important part of MFC, ClassWizard, it's completely broken. At least win95 improved many things over 3.1, but for MFC, I don't think that's the case. Just compiler is better, and that's the part I can't see.;) I suggest he should download 90 day trial of VS 2005 professional and test it, before upgrade. And of course disable intellisense during this test time. I'm sure in the end, he will stick with VS 6.0.
// "Life is very short and is very fragile also." Yanni
while (I'm_alive)
{
cout<<"I love programming.";
} -
Chris Losinger wrote:
the resource editor is a pain. etc.
It started to suck real bad in VS.NET 2k3, which is one of the reason why I do much resource editing directly in the .rc file these days. Feels like a step backwards... :~
-- Raaaaaaaaaaaaaaaaaaaaa!
Joergen Sigvardsson wrote:
Feels like a step backwards.
it is. it's the VB resource editor paradigm.
-
rrrado wrote:
IDE seems to by much slower and class view maybe more buggy that in 6.0 (it showed no members for SOME of my classes, even simple class).
I've had the opposite experience - Class View and Intellisense both were usually broken for me using VS6, especially when dealing with templates. The whole "browse info" thing felt tacked on and wasn't worth the additional build time - VS2005's ability to navigate through large class structures without an explicit build step has been very useful.
rrrado wrote:
2. compiling is also insanely slow.
Make sure you have plenty of memory, and have configured pre-compiled headers properly - on one project, I saw compile times drop from nearly an hour before configuring PCH to just under 20 minutes - only slightly longer than in VC6. Frankly, the improvements to the compiler and standard libraries were worth it for me - and the debugger is so much better it's not even funny; i used the VS2005 debugger for close to a year before moving to VS2005 for builds. The IDE itself has some issues, but frankly it's a half-decent text editor - i can live without the wizards.
every night, i kneel at the foot of my bed and thank the Great Overseeing Politicians for protecting my freedoms by reducing their number, as if they were deer in a state park. -- Chris Losinger, Online Poker Players?
Shog9 wrote:
I've had the opposite experience - Class View and Intellisense both were usually broken
Shog9 wrote:
The IDE itself has some issues, but frankly it's a half-decent text editor
I'm pretty sure you are not doing most of your work in MFC IDE, or you have a mainframe;). I tested it for over a month, and did all I could to continue using it. I failed, because I was spending more time to fight the slow IDE and the lost ClassWizard rather than coding. It also was a good reason to loose focus. As mentioned in another post, my best suggestion is that, he uses a 90 day trial of VS 2005 professional and check everything himself.
// "Life is very short and is very fragile also." Yanni
while (I'm_alive)
{
cout<<"I love programming.";
} -
Shog9 wrote:
I've had the opposite experience - Class View and Intellisense both were usually broken
Shog9 wrote:
The IDE itself has some issues, but frankly it's a half-decent text editor
I'm pretty sure you are not doing most of your work in MFC IDE, or you have a mainframe;). I tested it for over a month, and did all I could to continue using it. I failed, because I was spending more time to fight the slow IDE and the lost ClassWizard rather than coding. It also was a good reason to loose focus. As mentioned in another post, my best suggestion is that, he uses a 90 day trial of VS 2005 professional and check everything himself.
// "Life is very short and is very fragile also." Yanni
while (I'm_alive)
{
cout<<"I love programming.";
}Hamed Mosavi wrote:
I'm pretty sure you are not doing most of your work in MFC IDE
I do less work in MFC now than i used to, but it's still a factor. That said, I'd pretty much stopped using the Class Wizard in VS6 long before VS2005 came out - i didn't like its reliance on "special" comments for parsing source files, and really didn't like how much it complained when those comments came up missing. I want my code to look a certain way, and if the tools don't like it then i don't use those tools. As for the machine, i just upgraded my primary development machine (laptop) after a couple of years using (often multiple instances of) VS2005 on it - a 2.2Ghz Centrino with 1.5GB RAM and a dog-slow harddrive. The key is to 1) install the service packs or hotfixes so that the Intellisense thread doesn't hog processor time, and 2) configure PCH properly. There are also a ton of debugger tweaks to make things quicker there, but the "glorified text editor" portion mostly just works (with the hotfixes).
every night, i kneel at the foot of my bed and thank the Great Overseeing Politicians for protecting my freedoms by reducing their number, as if they were deer in a state park. -- Chris Losinger, Online Poker Players?
-
Another possible way to get VS6 is through a subscription to MSDN. That's quite expensive, but last time I checked, you could still get old products like VS6 if you're a subscriber. Also, as you've seen in this thread, some people seem to like the newer VSs better. Maybe somebody somewhere who no longer uses VS6 might have their copy for sale. (No I don't. I don't have an installation CD for it either. Wish I did.) BDF
VC6 isn't in MSDN anymore. MS had to stop shipping all products that contained their Java VM, thanks to all the legal crap with Sun.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Hungarian notation FTW
-
The Athlon 1800+ is a terrible processor, I had two and they were both pathetic. I found a thunderbird 1.3 Ghz and I got better better performance. But four minutes isn't that bad, the project I am working on takes between 8 and 9 minutes. I have to make the display look "pixel perfect" so I spend alot of time making changes and recompiling. Also, I find the 2005 IDE a lot more productive than 6 (but this is really preferance). And on a side note I like 2008 even more.
-Matt Newman
-
welcome to the world of software improvements. Compair the speed of windows 3.1 with XP on the same computer to get the idea. (if you could find a computer that would run both:omg:)
-
Matt Newman wrote:
The Athlon 1800+ is a terrible processor
Is it? I've got one in an old box and it was nothing but reliable, performance wise I can't remember that much.