次の方法で共有


Visual C++ 2008 Feature Pack shipped

In early January, we delivered a Beta of the Visual C++ 2008 Feature pack. I am pleased to announce that the Visual C++ 2008 Feature Pack has shipped!

The Feature Pack provides several exciting features for C++ developers, such as a major update to MFC and an implementation of TR1. Using the included MFC components, developers can create applications with the “look & feel” of Microsoft’s most popular products – Microsoft Office, Visual Studio and Internet Explorer. New components include the Office 2007 Ribbon Bar, Visual Studio docking and auto hide windows, Vista theme support, “on the fly” menu and toolbar customization, Shell management classes and much more. Our implementation of TR1 contains a number of important features such as smart pointers, regular expression parsing, containers (tuple, array, unordered set, etc) and sophisticated random number generators.

This product is a freely available download to any Visual Studio 2008 Standard or above customer and is fully covered under Microsoft’s standard support policies.

 

You may also want to take a look at the online documentation and walkthroughs for both MFC and TR1. The MFC documentation provides some great content to get you up and running quickly with the new components.

Namaste!

Comments

  • Anonymous
    April 07, 2008
    Thanks for this. Good to see C++ getting its fair share of support from MS. Will be nice if MS could release nice rich wrapper libs (hiding some COM specifics) to make development easier and more productive on C++ on Windows platforms. COM is what makes developers wary of jumping from Unix world onto the Windows native development bandwagon.  Just my 1c...

  • Anonymous
    April 07, 2008
    thank you for great news, C++ is longly used for many custmors around my job. Anyway, hyperlinks on MFC and TR1 are broken, I guess some server error happend on their site.

  • Anonymous
    April 07, 2008
    Great, all I need now is for them to update XNA so it works with 2008 and I'll be laughing :)

  • Anonymous
    April 07, 2008
    Sawai-san, I am not sure which hyperlinks you are referring to.  I just tried again the MFC and TR1 links from the post and it seemed to work well. -somasegar

  • Anonymous
    April 07, 2008
    By doing this you've chosen one third-party MFC control vendor who will survive, and put the rest out of business. I hope you're happy.

  • Anonymous
    April 08, 2008
    Has anyone else noticed that these are mostly features that have been available in the .NET framework for a while now?  It seems to me that Micro$oft is making the transitional push away from unmanaged code by making it second fiddle to managed code.  I'm not trying to bash C++, I'm just saying that this will be a reality far sooner than alot of people want to admit.

  • Anonymous
    April 08, 2008
    The comment has been removed

  • Anonymous
    April 17, 2008
    The comment has been removed

  • Anonymous
    April 17, 2008
    Hi Mesan, The team is working on a .NET ribbon control and we hope to have something around the end of this calendar year. -somasegar

  • Anonymous
    April 21, 2008
    [原文发表地址] Visual C++ 2008 Feature Pack shipped [原文发表时间] Monday, April 07, 2008 11:50 AM by Somasegar 在

  • Anonymous
    June 15, 2008
    Hi I wanted to report a bug: the regex class does not work with WCHAR and ECMA/icase (ECMA with for case insensitive). std::tr1::wregex rx(L"^([a-z0-9!#$%&'*+-/=?^_`{|}~]|(?!^).(?!.|$)){1,64}$|^"([\x01-\x08\x0b\x0c\x0e-\x1f\x20\x21\x23-\x5b\x5d-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f]){1,64}"$", (std::tr1::regex::flag_type)(std::tr1::regex_constants::ECMAScript | std::tr1::regex_constants::icase)); if (!std::tr1::regex_match((LPCWSTR)EMailAddressStringW.Left(iPos), rx)) return eInvalidChars;

  • Anonymous
    November 26, 2008
    Publicación del inglés original : Viernes, 21 de noviembre 8:36 AM PST por Somasegar Como parte de la

  • Anonymous
    December 04, 2008
    Hi, Does Visual C++ 2008 Feature Pack  includes Unit Testing plugin for VC++ projects as well? How to create a Automated Unit Test Cases for VC++ methods? Awaiting your response at the earliest. Thanks and Regards Krishnamurthy

  • Anonymous
    December 05, 2008
    Hello Krishnamurthy, The Feature Pack does not include any updates to unit testing. I would recommend taking a look at http://msdn.microsoft.com/en-us/library/ms243171.aspx & http://www.codeguru.com/columns/kate/article.php/c11893/ for VC++ unit testing. Also, you might find http://social.msdn.microsoft.com/forums/en-US/vststest/thread/cc3b7b31-e364-43c2-b40e-6b9013595a42/ useful. Thanks, Ayman Shoukry Visual C++ Team

  • Anonymous
    December 07, 2008
    Dear Ayman, Thanks a lot for the links. How do I create Unit Tests for Unmanaged Code? How do I create a Unit Test case for MFC and Static Library Code? I have created a Unit Test case for Class Library code by changing the /clr to /clr:safe. Kindly let me know the best practice to create a Unit Test case for MFC and Static Library Projects. Awaiting your response at the earliest. Thanks Krishnamurthy Dixit

  • Anonymous
    December 08, 2008
    We do not have a pure native unit testing solution, the only way to test native code is from Managed C++ via P/Invoke. Thanks, Ayman Shoukry

  • Anonymous
    December 09, 2008
    The comment has been removed

  • Anonymous
    December 09, 2008
    Hello Thomson, There should be no problems there. I believe the feature pack won't install if you already have VC2008 SP1 installed on your machine. The features introduced by the feature pack are already rolled into the service pack. If the feature pack is failling and you don't have the SP installed, then try installing the SP to get the features. If that is not a prefered choice, please feel free to contact me directly at aymans at microsoft dot com and we can try diagnosing the problem. Thanks, Ayman Shoukry Visual C++ Team

  • Anonymous
    December 09, 2008
    Thank you for your response Ayman, I did have SP1 installed. I have two installations (one worked, and one didn't) and I thought each had SP1. Turns out one of the systems was running XP did not have SP1, so I incorrectly concluded that it might be a vista thing.

  • Anonymous
    November 01, 2009
    The comment has been removed