C# vs VC++
-
Hello all, I am in the process of teaching myself VC++. However, I have received conflicting information about weather or not this is a waste of time. One friend of mine tells me that VC++ and MFC are the way to go, and that C# will not be utilized by many independant companies because of having to use the .NET framework. On the other hand, another friend of mine (also a developer) tells me that I am wasting my time with MFC and that the future is with C#. I was just wondering what your humble opinions on this subject are. Thanks in advance, Jobu --All the good themes have been used up. They've been turned into theme parks.
-
Hello all, I am in the process of teaching myself VC++. However, I have received conflicting information about weather or not this is a waste of time. One friend of mine tells me that VC++ and MFC are the way to go, and that C# will not be utilized by many independant companies because of having to use the .NET framework. On the other hand, another friend of mine (also a developer) tells me that I am wasting my time with MFC and that the future is with C#. I was just wondering what your humble opinions on this subject are. Thanks in advance, Jobu --All the good themes have been used up. They've been turned into theme parks.
Learn both, then it doesn't matter -- Help me! I'm turning into a grapefruit!
-
Hello all, I am in the process of teaching myself VC++. However, I have received conflicting information about weather or not this is a waste of time. One friend of mine tells me that VC++ and MFC are the way to go, and that C# will not be utilized by many independant companies because of having to use the .NET framework. On the other hand, another friend of mine (also a developer) tells me that I am wasting my time with MFC and that the future is with C#. I was just wondering what your humble opinions on this subject are. Thanks in advance, Jobu --All the good themes have been used up. They've been turned into theme parks.
There will always be a need for VC++ programmers, there is just far too much code out there to throw away. So learning VC++ is a good thing. The future for MFC is not clear at the moment. I suspect that Microsoft will introduce a new framework for writing C++ applications for the .NET platform. C# will take a while to catch on, but I have no doubt that it will succeed. I'd certainly consider learning both if I was starting out now. Michael :-) Logic, my dear Zoe, merely enables one to be wrong with authority. - The Doctor
-
Hello all, I am in the process of teaching myself VC++. However, I have received conflicting information about weather or not this is a waste of time. One friend of mine tells me that VC++ and MFC are the way to go, and that C# will not be utilized by many independant companies because of having to use the .NET framework. On the other hand, another friend of mine (also a developer) tells me that I am wasting my time with MFC and that the future is with C#. I was just wondering what your humble opinions on this subject are. Thanks in advance, Jobu --All the good themes have been used up. They've been turned into theme parks.
Wrong comparism. Java vs C# is more like it. C/C++ is a different kettle of fish. As regards ur question: learn both. C++ will always be needed: what are device drivers gonna be written in? VB? Anyway, I don't think that Microsoft are gonna port the millions of lines making up Windows over to C# anytime soon. Why are people always predicting the end of C++? C is such a useful language that it has been around for around 30 years. bibamus, edamus, cras moriemur [eat, drink, for tomorrow we die]
-
Hello all, I am in the process of teaching myself VC++. However, I have received conflicting information about weather or not this is a waste of time. One friend of mine tells me that VC++ and MFC are the way to go, and that C# will not be utilized by many independant companies because of having to use the .NET framework. On the other hand, another friend of mine (also a developer) tells me that I am wasting my time with MFC and that the future is with C#. I was just wondering what your humble opinions on this subject are. Thanks in advance, Jobu --All the good themes have been used up. They've been turned into theme parks.
The dichotomy is false. As has been said, there are places where C# will be useful, and places where C++ will remain the best tool. I think MFC is probably on it's last legs though. I'd not put too much time into MFC now, but I'd still learn it. Christian I am completely intolerant of stupidity. Stupidity is, of course, anything that doesn't conform to my way of thinking. - Jamie Hale - 29/05/2002
-
Hello all, I am in the process of teaching myself VC++. However, I have received conflicting information about weather or not this is a waste of time. One friend of mine tells me that VC++ and MFC are the way to go, and that C# will not be utilized by many independant companies because of having to use the .NET framework. On the other hand, another friend of mine (also a developer) tells me that I am wasting my time with MFC and that the future is with C#. I was just wondering what your humble opinions on this subject are. Thanks in advance, Jobu --All the good themes have been used up. They've been turned into theme parks.
If you don't want to bear the heavy overhead caused due to having to learn a new language, you can use Managed C++ instead of C#. That way you can mix MFC and .NET and ATL/WTL/STL and native API stuff all in the same cpp file. Nish
Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]
-
Learn both, then it doesn't matter -- Help me! I'm turning into a grapefruit!
-
Hello all, I am in the process of teaching myself VC++. However, I have received conflicting information about weather or not this is a waste of time. One friend of mine tells me that VC++ and MFC are the way to go, and that C# will not be utilized by many independant companies because of having to use the .NET framework. On the other hand, another friend of mine (also a developer) tells me that I am wasting my time with MFC and that the future is with C#. I was just wondering what your humble opinions on this subject are. Thanks in advance, Jobu --All the good themes have been used up. They've been turned into theme parks.
Jobu wrote: I am in the process of teaching myself VC++. As you are learning, keep in mind that there is a difference between Microsoft Visual C++ and the ANSI C++ language. When most people start to learn VC++ they really start learning how to use the MFC library. If the job situation later causes them to move to a pure C++ environment, they may be surprised at how little they really know about the C++ language. IMHO MFC has been a useful tool for developing windows apps but is slowly being phased out. If you can manage it, I think you would be best off learning both C++ (with MFC) and C#. But I wouldn't recommend learing both concurrently unless you have significant (several years) programming experience in other languages. BTW, my most used reference books for VC++: Programming Windows with MFC, Jeff Prosise The C++ Programming Language, Bjarne Stroustrup marshall If you continue to do the same things you always did,
don't be surprised if you get the same results you always got. -
If you don't want to bear the heavy overhead caused due to having to learn a new language, you can use Managed C++ instead of C#. That way you can mix MFC and .NET and ATL/WTL/STL and native API stuff all in the same cpp file. Nish
Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]
Nishant S wrote: That way you can mix MFC and .NET and ATL/WTL/STL and native API stuff all in the same cpp file. but would that be the best thing to do? To me, managed c++ is best used for the bits of code you need to call from your .NET apps. Something that should be used only when needed. Mixing too many technologies will soon become a maintainance nightmare. Michael :-) Logic, my dear Zoe, merely enables one to be wrong with authority. - The Doctor