C# Intended To Replace C++ ?

Certain (aspects of) applications which were previously done in c++ can now be done much easier using .net, such as gui programming and boring office apps, but i can't see c++ being totally replaced. C++ has access to all the windows functions, and you do advanced stuff like kernel programming which i don't think you can do with .net. If c# was meant to replace manged c++ then i doubt they would have created managed c++. managed c++ is great when you want to combine managed and unmanaged code.

Both C# and managed C++/C++/CLI have their place. Personally I'd use C# with p/invoke for just about everything, but I've used managed C++ projects in the past to fix problems.

Darwen.

If you look at how various languages and features have evolved, once upon a time there was Visual Basic and Visual C++, and there were Office programs. Office programs had their own built-in scripting language for writing macros.

Visual C++ could compile standard C++ code but also came with the MFC library.

Inter-process communication was done with DDE. Then came the improved OLE and COM and COM remained stable for a while. VB was Microsoft's "pet" language, and the Office macros were changed to use VB.

Meanwhile programming evolved further, we got multi-threading, more network-connections, internet etc. Java came along with in-built library features and could run on any platform that had a virtual machine. Java is owned by Sun OS so Microsoft had to come along with their own variety, and C# emerged. Meanwhile the COM framework had its many problems, so was replaced by .NET.

With C# now being Microsoft's new pet language, they effectively designed C# around .NET so it would fit the model perfectly, then started adding support for other languages.

In my opinion, many people who used MFC as their GUI have changed to C# under .NET. While they didn't dare touch VB, C# is a much better language (more OO) and there is a general feeling that it's a language that's useful to know (lots of jobs in it) so they make the effort to learn it.

Those who were writing C++ under COM have also moved over to .NET. They may use C# again as the native language.

Apps ported from C++ may be ported into CLI because it's probably easier to port to than to C#. I don't know if many new apps are written in CLI but there are no doubt a few that will favour it.

Often the decision to write in one language rather than another is taken because the particular language happens to be more popular at the moment. A lot of programs were written in Java for that reason in the late 90s/early 00s just for that reason.

No, why it should? C++ is for manipulating memory, C# is for manipulating objects. In C++ (or lower languages), you can touch hardware directly, it is much better language to write OS and drivers than C#. Writing OS in C# is as fool idea as write business web application in C++. There allways must be language with lower capabilities like in C++ to write CLR or JVM or other virtual machine.

C++ and C# will keep their place, at least revolutionary new hardware will be developed. However, C# will take more and more portion of common daily developer's work.

well managed C++ and c# are the same really. you have access to the same libraries and can do the same thing. the only difference is in the syntax, and even that isn't a world away from c# syntax. dot net (any language) and unmanaged c++ complement each other very nicely.

I have forgotten this, but it doesn't change my opinon. C# (.NET respectively) can became the primary OS language (or better - platform how to comunicate with the OS) as Objective-C is of NextStep. But you need a VM (or CLR in case of .NET), which cannot be written in C# directly, because it MUST be able to control the hardware directly. By OS, I mean scheduler, memory manager, I/O facilities and so on which I cannot imagine to be written in higher language like C#. OS can be unified with CLR, but never could be written without knowleadge and usage of underlying hardware.

I have forgotten this, but it doesn't change my opinon. C# (.NET respectively) can became the primary OS language (or better - platform how to comunicate with the OS) as Objective-C is of NextStep. But you need a VM (or CLR in case of .NET), which cannot be written in C# directly, because it MUST be able to control the hardware directly. By OS, I mean scheduler, memory manager, I/O facilities and so on which I cannot imagine to be written in higher language like C#. OS can be unified with CLR, but never could be written without knowleadge and usage of underlying hardware.

One of the videos(cant remember) which says it is impossible unless we have a managed processor (instead of native processor). LOL.