Here is an article about Managed C++ from July 2002!
https://www.codeproject.com/Articles/1479/Introduction-to-Ma...
There are others when searching from 2002 articles.
Mono did try to port them as well,
https://www.mono-project.com/docs/about-mono/languages/cplus...
So you see, the information is out there.
That is how Mono started.
Additionally here is some historical refreshing about two other attempts,
https://www.gnu.org/software/dotgnu
https://www.codeguru.com/dotnet/net-nuts-bolts-the-joy-of-ro...
A surviving clone of the repo is available here,
https://github.com/SSCLI/sscli_20021101
Finally, this doesn't change the fact that the CLR was only yet another version of this idea, there are plenty of others since UNCOL in 1958.
I'm not saying it changes anything. Wasm is just a more modern attempt, like .NET itself. I don't see any reason to prefer one or the other only because of its age.
It is not like all those beautiful WASM implementations support the same set of features, from the paper standard,
Wasm is much newer than Mono was at the time. Let's wait.
Well, if it so easy to build vanilla C/C++ code for .NET then Microsoft is definitely doing a very poor job promoting this feature ;)
Does the cross-platform dotnet toolchain support building C/C++? I never saw this mentioned when reading about dotnet (it was always about C#).