C ++/CLI is not used to write applications

Supports compilation of machine codes and. net-managed code C ++/CLI, formerly managed C ++, basically equivalent to a C ++ and a C ++ style.. NET language. Programmers like powerful languages and can understand them. Many people use C ++ because C ++ is very powerful. However, being powerful is not always good at all aspects of the system. So far, it is mainly used for interaction between hosted and non-hosted programs, packaging unmanaged code into a hosted class library. However, using it to write. Net Applications does not have advantages or are not the focus of Visual Studio support. For example, the WPF editor does not support C ++/CLI.

 

In addition to packaging, C ++/CLI is used to compile the old c ++ program into. NET platform code with minimal changes. At present, CPU hardware is becoming more and more heterogeneous, 32-bit, 64-bit, arm is emerging, and various embedded processors are becoming increasingly important for one-time compilation and multiple operations .. The. NET Runtime Library provides the ability to build a cross-hardware platform for C ++. However, this protects the legacy C ++ code assets.

 

In recent years, the focus of Vc has been on native code, largely because the C ++ user group lacks sufficient interest in hosting platforms.

What is the future of C ++/CLI?
Posted Microsoft
On 12/4/2008 at pm we will continue investing
In C ++/CLI to enable developers to expose native C ++ assets to
Managed world and vice versa. We believe that pure. NET development is
Done best using a. Net focused language such as C # Or VB. Investing in
C ++/CLI will be mainly in the native-managed InterOP areas.

Thanks,
Ayman Shoukry
Visual c ++ team postedPavel minaev [MSFT]
On 11/15/2008 at 12:31 pm imo, it was second-class
From the very beginning (e.g. It didn't support ASP. NET, etc). It's
Still a great tool to integrate native libs into managed apps, and that
Seems to be its primary niche.