Reputation: 776
Is it recommendable to use C++/CLI as main language for a new .Net application? The application won't use native code (pure CLI). The reason for this question is, that I want to use the framwork but not leaning a new language like C# or VB.
Stefan
Upvotes: 0
Views: 171
Reputation: 942308
It is not. Microsoft stopped development on the language, it is in maintenance mode. None of the innovations made in C# and VB.NET since 2005 were added to the language, Linq and dynamic dispatch being the heavy ones. While IDE support was already weak, VS2010 shipped without IntelliSense support for the language, another nail in the coffin.
It is going to be maintained, the language is still core to parts of the .NET framework. Notably System.Data and WPF heavily rely on it. And it is still the primary choice for difficult native interop. But with the lack of support in the IDE, it just isn't suitable as a first-choice language. Rather a problem for programmers that get their start with the Express edition of C++ btw, there is no other decent GUI programming solution in that SKU.
Upvotes: 3
Reputation: 67487
You would be learning a new language anyway, managed C++ is nothing like C++. I would just go with C#, it's as close to C++ as managed C++ is, only it's a lot less verbose and has a ton more features (auto implemented properties, auto implemented iterators, lambda expressions etc).
Upvotes: 7
Reputation: 888177
C++/CLI is designed for interop scenarios.
It is strongly recommended that you use C# for new development; it will be much simpler.
You should not be afraid of learning a new language. Most of C#'s learning curve is for .Net itself; using C++/CLI won't save you much learning.
Upvotes: 7