57 minutes ago, Josheir said:
I thought managed code for Visual C++ was using CLR which was "getting ready" for dot net. And than that got deprecated.
Ok, so quick history lesson:
When dot net came out, Microsoft wanted a way to integrate C++ into it. The intention was never really to write .Net code in C++ but to provide a bridging layer so you could call a C++ library from .Net.
So Microsoft created Managed C++, a set of extensions to C++ that allowed C++ to use the CLR. Technically, they were following the C++ standard for adding extensions to the language. Unfortunately, it was butt ugly and everyone hated it.
In 2005, they replaced it with C++/CLI (C++ modified for Common Language Infrastructure). This was much easier to use and is still in use today. It's not the preferred way to write .Net, but if you have an existing C++ codebase you want to use from .Net, it's actually pretty good.
And finally there's C++/CX, which is not .Net but C++ for the WinRT platform. You don't really need to worry about it unless you want to write UWP apps. I only mention it in case you happen to see it.
If you'd like to read more on the history of this, there's an excellent (if slightly dated) article on Ars Technica.
if you think programming is like sex, you probably haven't done much of either.-------------- - capn_midnight