I heard somewhere that Microsoft will be focusing their efforts on C# rather than C++ for the .NET platform. I can see signs of this being true because of the GUI designer that was available for C# but not C++.
So I would like to know if C++ in .NET is dying and if it will continue to be second to C# in the future.
It is not dead, and it will not be in the foreseeable future. The . NET Core updates may have distressed many developers. They may not be able to use the major functions of the original platform due to significant modifications made by unifying the .
The . NET framework isn't dead; it just won't be developed by Microsoft anymore. Many other organizations are committed to its continued use and development, including Xamarin and Unity. That said, there is a big question of what will happen to the apps written in .
C# is a programming language that is worth learning. You can use it as a Full Stack language and programming in C# will be the best decision. In 2022, It will be a widely used language and is widely recognized among other programming languages such as Java and Python.
This doesn't mean that C# is not mature, it just means that it is a young language compared to the other languages out there, and that it is much better than you probably think, so C# is not dying because it is built and maintained by Microsoft.
If you are targeting the .NET framework in application development then yes C++/CLI is a second class citizen compared to C#. C# was specifically designed as the language for .NET framework meanwhile C++/CLI extension is there to allow developers to bridge native and managed code.
However do not confuse C++ with C++/CLI (C++ .NET is the same thing...). C++ is alive and well in areas such as the kernel, games, high-performance and server apps (e.g. SQL server) all of which are unlikely to change. On the other hand most .NET 'GUI stuff' won't use C++.
Managed C++ never really got to be what MS thought it would be. C# could do (nearly) the same thing, with a lot more intuitive and user-friendly syntax.
Apart from that, C++/CLI will not be left unsupported for a long time, as it's the easy way to create interop between .NET assemblies and native C++ assemblies. That's about all it's used for though (I'm sure there's a 0.001% of C++/CLI developers out there who disagree :P ).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With