xboxscene.org forums

Author Topic: Visual C++ 6.0 Vs. Visual C++.net?  (Read 40 times)

fghjj

  • Archived User
  • Sr. Member
  • *
  • Posts: 288
Visual C++ 6.0 Vs. Visual C++.net?
« on: August 30, 2004, 04:40:00 PM »
It's all C++, but sometimes bookauthors tend to use stupid custom frameworks in all their examples or use non-default libraries. If you want to begin with a simple console app for experimenting here's how:
CODE

#include

using namespace std;

void main()
{
   char sBuffer[128];
   int iNumber;

   cout << "Type text:" << endl;
   cin >> sBuffer;

   cout << "Type a number:" << endl;
   cin >> iNumber;

   cout << "You typed:" << sBuffer << endl;
   cout << "Number * 2 = " << iNumber * 2 << " Nice huh?" << endl;

   return;
}

As you see you can write anything to the cout object it'll try to make it look good on your console. endl means a newline and flush. Happy coding.
Logged

joseph_hac

  • Archived User
  • Sr. Member
  • *
  • Posts: 415
Visual C++ 6.0 Vs. Visual C++.net?
« Reply #1 on: August 30, 2004, 07:06:00 PM »
I went into college knowing Visual Basic 6.0. In my first week of class, I was asked to write a basic program in Visual Basic .NET. I very quickly wrote the program only to discover that it had build error after build error. After a couple of weeks, I got use to .NET, and now I probably couldn't write a program in VB 6.0 if I tried.
Logged

Brouhaha

  • Archived User
  • Full Member
  • *
  • Posts: 213
Visual C++ 6.0 Vs. Visual C++.net?
« Reply #2 on: August 31, 2004, 06:44:00 AM »
Visual Studio, wether it be .NET or 6.0, is only the IDE.  Although Visual Basic has changed a lot (it is now fully Object Oriented and compiled to MSIL just like C# and other languages supported by the framework), C++ is pretty much the same as it was in Visual Studio 6.0. How come? C++ is fully compiled as opposed to the other languages supported by the IDE.  Meaning that it is the only language that you can build framework-free applications with in Visual Studio .NET.

Do not mix up Managed C++ and plain C++.  Every C++ project type that has (.NET) at the end mean that is managed and that it will be bound to the framework, but with added functionnalities.

Good luck!

Logged

ragnar999

  • Archived User
  • Newbie
  • *
  • Posts: 19
Visual C++ 6.0 Vs. Visual C++.net?
« Reply #3 on: September 15, 2004, 07:34:00 AM »
So VS6 C++ is plain C++ and means the compiled exe can be run on any PC, while .NET is managed and can only run on PC's that have .NET framework installed on them, is that what you are saying?

If so then id'e stick to plain C++
Logged

Brouhaha

  • Archived User
  • Full Member
  • *
  • Posts: 213
Visual C++ 6.0 Vs. Visual C++.net?
« Reply #4 on: September 15, 2004, 11:05:00 AM »
QUOTE

So VS6 C++ is plain C++ and means the compiled exe can be run on any PC, while .NET is managed and can only run on PC's that have .NET framework installed on them, is that what you are saying?


With Visual Studio .NET, you have the possibility to use managed C++ OR good old C++ just like in Visual Studio 6.

If you choose to use good old C++, then the PC running the application will not need the .NET framework.  You can even open up old visual studio 6 projects and it'll convert them and compile them just fine.
Logged