C++/CLI?

C++/CLI?

• Tirrell

  Troff is correct, C++/CLI is the correct term for the language the VC team shipped in VS2005, and it's what we should be using. C++/CLI won't be going away anytime soon, as it's by far the fastest way to get existing, tested codebases running on .NET, and it's also the most performant (IIRC Managed DirectX is coded in C++/CLI for this reason). Many of the productivity benefits of C# translate over to C++/CLI as well, as you can access the form designer, etc.

  Cheers!

  Jeff

  
  
  

• Chris0144

  It specifically refers to the abomination that was the first "hack" to get C++ onto the CLR, you know, the one with all the __s. VS2005 ships with the new incarnation called C++/CLI which not only is a legal extension of C++, but feels like C++ and is an ECMA standard in its own right.
  
  

• James_N

  I'm sorry about that, but most developers don't really care for Managed C++ so it won't be available any time soon. As to why it's not "just works" please see this:

  http://groups.google.com/group/microsoft.public.dotnet.framework.compactframework/browse_frm/thread/baaaa97add932951/4fc4d7f875f89081#4fc4d7f875f89081

  
  
  

• AndyLee71

  Why That's what it is and the term is everywhere.
  
  

• Triple B

  You sure can use C++, but native only. Managed C++ support was never promised:

  http://groups.google.com/group/microsoft.public.dotnet.framework.compactframework/browse_frm/thread/a184d802972e440c/d8f4085cc37d6d39#d8f4085cc37d6d39

  
  
  

• Chris Du

  Well, I think I'm mistaken. The old term was probably something like Managed Extensions. For whatever it's worth, I think it's quite well stuck among its prospective users already.
  
  

• farproc2000

  That is an enormous disappointment. What would it take that VS2005 doesn't already have
  
  

• Ertan Köseler

  I see. I doubt, however, this new term would stick as old one is actually describing the nature of the product really well. Besides, it’s too late, the term is already out. Compare, for example, Google search results for both.

  Personally, I consider this a temporary solution to allow legacy C++ code to run on .Net. In my opinion it does not have long to live as it combines worst properties of C++ (e.g. code complexity) and .Net (performance hit, CLR dependency, no real time support). I would go with C# for increased reliability and productivity or for native C++ if I have to.

  
  
  

• OPL

  Thanks. Could you please stop using the term "Managed C++"
  
  
• C++/CLI?