Microsoft Tells What's Next for C++

Microsoft Tells What's Next for C++

  • Comments 64

 By chance,  are you among those who think that Microsoft is leaving native development in general and the C++ programming language in particular behind? You better watch this interview to Ale Contenti, Principal Development Manager with the Windows C++ team at Microsoft.

Click here to play this video

[Can't see the video player in this page? Try Channel9]


The interview was made by Christian Binder, Platform Strategy Manager with Microsoft Germany and Development Practices track owner in the still recent TechEd Europe 2010. Ale talks about key differentiators C++ offers today to developers, before other programming alternatives, but he also clears up any suspicion about Microsoft commitment to the language created by Bjarne Stroustrup by listing the efforts Redmond is doing for its evolution.

Ale had also delivered a session on ALM for C++ in that same conference.

Leave a Comment
  • Please add 8 and 7 and type the answer here:
  • Post
  • Making the F1 help in VS work properly for native Win32 developers would be a good sign of support for C++.

    I heard it was going to be improved in VS2010 but found it was even worse than before (and it's been getting worse and worse since VC6). e.g. I push F1 over ::GetMessage and am given help about some managed interface to Windows Azure message queues. Wrong language, framework and platform. Sigh.

    It was bad enough when it used to bring up WinCE or MFC docs by mistake, now we get C# stuff with similar names... and even things for entirely the wrong platform.

    You can find this issue reported again and again by many, many people for YEARS in Connect, always closed and ignored.

    I've given up using the IDE for help and just search Google now.

  • We hoep some other company provide a good,fast,native-self IDE.

  • The same thing that Leo reported also occurs with Direct3D (at least Direct3D9, haven't checked with later versions). It shows not just a C# wrapper, but an *internal helper class* for the C# wrapper.

    I don't doubt your commitment to the C++ compiler, but the IDE could really use some help.

  • C++ is dead at Microsoft. It clearly shows up as a botched up job in VC2010. Wonder why the hell they used WPF for the IDE, It is so damn slow and frustrating. Even the compile times are way too behind than VS2008.

  • It's no question C++ is left behind. 95% of Microsoft's efforts go toward lowering the bar for scriptkids to create even more cookiecutter bloatfest monstrosities. Even the few areas of relative diligence, such as the compiler, are clearly behind the competition.

  • A good sign of improvement and investment in C++ would be to throw away the WPF editor and managed code in the new VS2010 IDE and just return to native C++ fast and low memory footprint stuff, return to VC6 quality F1 help experience, implements more C++0x features (seems like GCC C++0x status is more advanced than VC10), offer some quality C++ framework to do native Windows development, make the C++/CLI visualizers work correctly.

  • Where is the updated WTL? C++ looks totally abandoned and the VS2010 IDE is horribly slow (on a 6 cores 3.2GHz 12GB 64-bit machine!). The Intel compiler can optimize for SSE4.x and parallelize automatically (to some extent) and MS C++ still targets SSE2 from year 2001. Also everything seems to revolve around 32-bit development. If I create an ATL project ans just add x64 configuration, the unmodified wizard-generated code does not compile with a "TRACKER : error TRK0002: Failed to execute command... The handle is invalid." error. Makes me wonder if it was tested *at all*??? Moving the IDE to managed code and WPF was the worst mistake ever, losing menu customizations and adding nothing but slowness. And yes, the help system is a joke. I'm actually skipping VS2010 altogether, sorry, and no amount of inverviews will make me change my mind...

  • I agree with cplusplusrocks. Speed goes down and memory footprint goes up but it's been like this for almost 10 years ... "VC10 is the new 6 " they said, no comment ... I'm pretty sure a refreshed VC6 (compiler, properties, intellisense) will be much better than the Visual Studio suite.

    Will we see one day a modern and decent C++ framework? I have not much trust in the VC++ team, let's hope the revolution will come from the Windows team ...

  • Something like the QT framework would be awesome.

  • Yes "Something like the Qt framework would be awesome"

  • a new framework like the Qt framework would be very awesome

  • Sadly everyone who has commented on this is 100% right. I've used all versions of Visual C++ from 6 onwards. VS 2003 was the last half decent one, and VC++ 6 was the last brilliant one and is now 12 yrs old! Not disputing that compilers are good, but the IDEs are a defocussed mess that need to refocus, and debloat and get debugged properly.

    1) WTL 8.1 is stuck in beta hell.

    2) The help system still doesn't work, as Leo said and hasn't for years.

    3) SxS DLLs are a pain, fortunately this DID get fixed in VS2010 - I hated it in 2005/8

    4) The constant use of changing and incompatible solution/project file formats are a pig. Parsing the VS2010 ones can take so long now that Win7 can think the IDE has hung...

    5) VS2010 wasn't the new 6, it wasn't even the new 2003. (Sorry Damien Watkins!)

  • I completely agree about F1. It's just useless. I've given up long ago. I now use chrome+google for getting MSDN documentation, works well. Judging from the level of commitment from MS to fix it, that mut be what the MS devs are doing themselves.

    VS2010 IDE is slow as molasses. After the mega-hype that VS2010 "was going to be the new VC6 for C++", I think what you pulled of was comparable only to Vista and Itanium.

    But what really left me completely mystified is, what the heck was this interview all about? I mean, nothing of any importance was actually said. Why use time for blabbering like this when you could finally roll up your sleeves and fix the product.

  • It seems clear that Microsoft no longer wants developers to use C++ for wathever reasons (if not convinced simply watch the .NET propraganda on Channel9 and what they say about native code).

    Isn't it called dumbing down?

  • Doesn't every one?  Not to be flippant, be doesn't every one just use google to find API docs?

Page 1 of 5 (64 items) 12345