Bjørn Roald wrote:
Edward Diener skrev:
Arkadiy Vertleyb wrote:
While Microsoft can be commended for raising the level of their compiler in VC7.1 and VC8, the truth is that where it matters commercially almost no new future work is being done in C++ and .Net, and this is directly the "fault" of Microsoft.
Or their hopefully failing purpose. I think the game here is as follows:
1. a lot of C++ code is out there 2. we want those projects tied up in, and eventually converted to our proprietary platform called .NET. 3. to convert those projects to .NET we need C++.net (i.e. managed C++) so they can be tempted to move in our direction 4. we create a set of C++ bindings to .NET (vs 2003) 5. oops, it failed --- almost nobody moved since it looked ugly
It failed because of the infamous loader lock bug ( http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechar... ). The syntax has been made better and easier to use from Managed C++ to C++/CLI, but that has little to do with the failure.