I have stayed with VC (through managed C++ and now C++/CLI) and stayed away from C#. Initially, because I did not want to learn a new language. BUT! the learning curve to C# could not have been more than what I went through to Mangaged C and then onto C++/CLI.
I am currently porting a complex C# control to C++. Hence, I'm seeing more C# than I have previously looked at in detail. And, I am impressed! C# does some things more directly than C++. So... Once again... I am thinking... I should have moved to C# 2 years ago. But... I'm still resistant. I like C++/CLI. I actually like the casts, pointers, and namespace qualifiers -- gives me a more solid feel.
But, I find, that C# is not just a fancy Visual Basic. If someone can give me a good reason to stay with C++/CLI I would like to read it. (I do interface work -- not web related.)
Last edited by BillG; June 21st, 2006 at 12:07 AM.
C# is a great language, and is actually my language of choice in most scenarios when developing pure, safe managed code. C++/CLI offers some nice linguistic goodies, such as templates, deterministic finalization, reference and value class semantics, etc. For some, these features are very compelling. For me, the most compelling feature of C++/CLI is the ability to smoothly interoperate with native code so that I can both leverage my existing code and build high performance software.