[RESOLVED] Why stay with C++ and not move to C#?
CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 4 of 4

Thread: [RESOLVED] Why stay with C++ and not move to C#?

Threaded View

  1. #1
    Join Date
    Jun 2006

    [RESOLVED] Why stay with C++ and not move to C#?

    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.
    Share on Google+

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Windows Mobile Development Center

Click Here to Expand Forum to Full Width

On-Demand Webinars (sponsored)