Home Dashboard Directory Help

strsafe.h triggers many warnings with STL header files by pgroke


 as Fixed Help for as Fixed

Sign in
to vote
Type: Bug
ID: 646532
Opened: 2/23/2011 4:33:32 PM
Access Restriction: Public
User(s) can reproduce this bug


Including <strsafe.h> before STL header files like <string> yields many warnings from inside the STL header files.

There is a simple workaround: include <strsafe.h> after all STL headers, but I still think this should be fixed. Just including a bunch of headers that ship with the compiler should not trigger any warnings.
Sign in to post a comment.
Posted by Microsoft on 3/1/2011 at 5:07 PM

Thanks for reporting this bug. We've already reported it to Windows, and they've already fixed it in the Windows SDK. This fix will be available in VC11.

If you have any further questions, feel free to E-mail me at stl@microsoft.com .

Stephan T. Lavavej
Visual C++ Libraries Developer
Posted by Microsoft on 2/23/2011 at 6:04 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 2/23/2011 at 5:14 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by AbdElRaheim on 11/7/2011 at 11:19 PM
#pragma warning( push )
#pragma warning( disable : 4995 )
#include <string>
#pragma warning( pop )