🔒 Locked
Visual C++
Advertisement
Original Post
Dev-C++/MinGW has finally annoyed me too much to touch it, so I''m looking at Visual C++. Mostly I want it so I can actually use the retail libraries for DirectX, but not crashing 4 times a day and having a functional variable watcher would be helpful too.
Which version should I get? 6, 7, or .NET? Does the .NET version allow you to compile code that doesn''t need the .NET runtime installed?
7 and .NET is the same thing, but you have .NET 2002 and 2003 (little difference).
"C lets you shoot yourself in the foot rather easily. C++ allows you to reuse the bullet!"
"C lets you shoot yourself in the foot rather easily. C++ allows you to reuse the bullet!"
Yes, you can compile to "normal" Windows binaries with VS .NET. Have no idea about the code folding. I haven''t seen the feature in VS6, but I haven''t seen it in VS .NET either.
[My Image Gallery (WIP)][Greatest Tetris clone evar!][Return your stolen MP3s]
[My Image Gallery (WIP)][Greatest Tetris clone evar!][Return your stolen MP3s]
Whomever recommends 6 should be shot. You WILL go insane while working with 6. It doesn''t work with templates correctly, it doesn''t work with anything correctly for that matter (well, most things). Visual C++ .Net or Visual C++ .Net 2k3 have much better compilers (2k3 being more standards compliant).
Spend some extra money and get Visual C++ .Net 2k3, you won''t regret it.
Spend some extra money and get Visual C++ .Net 2k3, you won''t regret it.
quote:
Original post by Raloth
But still... Will compiling with that require the .NET libraries installed on everyone''s computer who runs it?
And... Does 6 support code folding? Where I can minimize functions so I only see their name and a plus sign to the left to maximize them.
You can compile C++ programs that don''t even THINK about .NET, just like with VC6, except better
No, VC6 doesn''t support code folding, but VisualStudio.NET (that is the IDE for VC 7.0 and 7.1) does. Handy thing, at that.
.NET 2002 is v7, so is .NET 2003 v8 or v7.1?
SketchSoft OFFLINE | SketchNews OFFLINE | NewKlear Studios
SketchSoft OFFLINE | SketchNews OFFLINE | NewKlear Studios
If you''re a student you might try to get academic verison trough MSDNAA.
You should never let your fears become the boundaries of your dreams.
You should never let your fears become the boundaries of your dreams.
I use VS.NET Professional on windows 2000 with no problems. I don''t know if its any cheaper then WinXP pro, though. If it is, just upgrade to W2k =D
there is a website that sells software sans manuals and packaging, with like a 90% savings. But I can''t seem to find the damn link...
Ah, here it is, OEM Expert.
Ah, here it is, OEM Expert.
Something about me doesn''t like the idea of an "academic" version. I''m fine with paying the full $100 for VC++ (since programming is about all I do) but it''s the $200+ for the operating system that I feel ripped off about. Are there discounts available for XP? If I''m going to upgrade I''d rather just jump ahead to the top.
quote:
Original post by doodle_sketch
.NET 2002 is v7, so is .NET 2003 v8 or v7.1?
SketchSoft OFFLINE | SketchNews OFFLINE | NewKlear Studios
7.1
"C lets you shoot yourself in the foot rather easily. C++ allows you to reuse the bullet!"
quote:I have worked with VS6 for years, and I have not found any of these problems that you are talking about, nor have I gone insane. True, if I were to buy an IDE today, I would buy ver. 7, but 6 works fine for me.
Original post by Drevay
Whomever recommends 6 should be shot. You WILL go insane while working with 6. It doesn''t work with templates correctly, it doesn''t work with anything correctly for that matter (well, most things).
Also, with the new VS, wasn''t there something weird with the optimizations? Like only the professional and enterprise versions came with it or something
quote:
Original post by circlesoftquote:I have worked with VS6 for years, and I have not found any of these problems that you are talking about, nor have I gone insane. True, if I were to buy an IDE today, I would buy ver. 7, but 6 works fine for me.
Original post by Drevay
Whomever recommends 6 should be shot. You WILL go insane while working with 6. It doesn''t work with templates correctly, it doesn''t work with anything correctly for that matter (well, most things).
Also, with the new VS, wasn''t there something weird with the optimizations? Like only the professional and enterprise versions came with it or something
these people that complain are just elitists that HEARD somewhere there were "MAJOR PROLBESM OH TEH NOS!!!!1!" with VS6, and so now they just repeat them over and over.
I''ve done template classes in VS6 out of a book written for g++ and have had no problems.
quote:
Original post by capn_midnightquote:
Original post by circlesoftquote:I have worked with VS6 for years, and I have not found any of these problems that you are talking about, nor have I gone insane. True, if I were to buy an IDE today, I would buy ver. 7, but 6 works fine for me.
Original post by Drevay
Whomever recommends 6 should be shot. You WILL go insane while working with 6. It doesn''t work with templates correctly, it doesn''t work with anything correctly for that matter (well, most things).
Also, with the new VS, wasn''t there something weird with the optimizations? Like only the professional and enterprise versions came with it or something
these people that complain are just elitists that HEARD somewhere there were "MAJOR PROLBESM OH TEH NOS!!!!1!" with VS6, and so now they just repeat them over and over.
I''ve done template classes in VS6 out of a book written for g++ and have had no problems.
I don''t think it''s templates that vc6 has a problem with, but the STL. If I remember correctly, I couldn''t even cin >> string. And a friend of mine using a vector would randomly get garbage added to the begining of it when using push_back(), but it compiled and ran fine with g++. But for the most part you won''t have any problems.
Oh, and it also doesn''t enforce the ''using'' thing, you never have to do it but in g++ and .NET you do.
__________________________________________
I am Spiderman and I''m hitting things!
Eat the vegetarians!
quote:
Original post by Rixterquote:
Original post by capn_midnightquote:
Original post by circlesoftquote:I have worked with VS6 for years, and I have not found any of these problems that you are talking about, nor have I gone insane. True, if I were to buy an IDE today, I would buy ver. 7, but 6 works fine for me.
Original post by Drevay
Whomever recommends 6 should be shot. You WILL go insane while working with 6. It doesn''t work with templates correctly, it doesn''t work with anything correctly for that matter (well, most things).
Also, with the new VS, wasn''t there something weird with the optimizations? Like only the professional and enterprise versions came with it or something
these people that complain are just elitists that HEARD somewhere there were "MAJOR PROLBESM OH TEH NOS!!!!1!" with VS6, and so now they just repeat them over and over.
I''ve done template classes in VS6 out of a book written for g++ and have had no problems.
I don''t think it''s templates that vc6 has a problem with, but the STL. If I remember correctly, I couldn''t even cin >> string. And a friend of mine using a vector would randomly get garbage added to the begining of it when using push_back(), but it compiled and ran fine with g++. But for the most part you won''t have any problems.
Oh, and it also doesn''t enforce the ''using'' thing, you never have to do it but in g++ and .NET you do.
__________________________________________
I am Spiderman and I''m hitting things!
Eat the vegetarians!
I don''t know what you are talking about. I have to use "using" anytime I use <iostream> or <string> or whatever. It''s when you use <iostream.h> that you have problems. I''ve never had your problem with vector and cin>>string always works for me. Seriously, I have done EVERYTHING that has been mentioned so far, and I haven''t had any problems.
quote:
Original post by capn_midnight
I don''t know what you are talking about. I have to use "using" anytime I use <iostream> or <string> or whatever. It''s when you use <iostream.h> that you have problems.
OK, yeah, I forgot about that
quote:
I''ve never had your problem with vector and cin>>string always works for me. Seriously, I have done EVERYTHING that has been mentioned so far, and I haven''t had any problems.
For some reason it didn''t like the string thing on mine, and the vector thing I didn''t try first hand, but I know he stopped having problems without changing any code, just using a different compiler. Maybe you have a patched version of 6?
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement