Partager via

VC++ product strategy on Channel9

  • Article

Bill Dunlap and I had the opportunity to sit down with Charles Torre on Channel9 to talk Visual C++ product strategy.  We talk about the three-pronged product strategy for the product, which is:

  1. Support and add value to the native Windows API
  2. Provide for friction-free native/managed interop
  3. Modernize the C++ toolset

We also talk more specifically about some of the work we're doing for Orcas, including the marshaling library and STL/CLR, post-Orcas work we're doing on compiler front-end, cryptic comments on "big things" we're planning for MFC, and early thinking on concurrency and safer C++.

We also have a number of other Channel9 videos with other team members that will come online over the coming weeks that drill into more detail on our Orcas features.

Comments

  • Anonymous
    February 13, 2007
    The comment has been removed

  • Anonymous
    February 16, 2007
    Aaron, The WinForms designer already supports C++/CLI, and we also try to make it easy to build UIs in C# and integrate them with your C++ code using C++/CLI.

  • Anonymous
    February 17, 2007
    The comment has been removed

  • Anonymous
    February 17, 2007
    because end-user is more important than the developer its just a tradeoff wether to build an easy_to_use library/platform or a robust one. microsoft's strategy lately has been more on the earlier one (easy for the developers: enter C# 2.0)

  • Anonymous
    February 18, 2007
    Its there but you guys could do a better job of it.  I don't like the idea of switching languages between ui and business logic.  Not to mention its far more difficult to maintain and support. To be fair I made that comment before watching the video.  After seeing it I think your moving in the right direction. PS I find the C# ide lacking when it comes to large projects and  complicated logic.

  • Anonymous
    February 20, 2007
    zakimirza: easy of use and robustness don't necessarily have to be mutually exclusive, but certainly the more power and flexibility the framework exposes, the more difficult it is to make the framework simple to use.  I believe our choice of investment directions for C++, though, will pay dividends for those focused on building large-scale software. Aaron: Glad you like the direction.  We've come to realize that we simply cannot do everything C# and VB do and do everything that needs to be done for native code developers.  Brilliant interop technology has to be a key part of our strategy for bridging the gaps.

  • Anonymous
    February 23, 2007
    The comment has been removed

  • Anonymous
    February 26, 2007
    Wil: I believe I've addressed this issue of .NET language neutrality vis-a-vis C++ in this previous blog posting: http://blogs.msdn.com/texblog/archive/2005/07/19/440621.aspx