ATL and MFC changes and fixes in Visual Studio 2013
Hello, I’m Pat Brenner, a developer on the Visual C++ Libraries team. In this blog post I would like to share with you the changes that we’ve made in ATL and MFC for Visual Studio 2013.
One of the major changes we made was to eliminate the ATL DLL altogether. All ATL code is now static, either in the header files or in the ATL static library. We also reduced the amount of code in the ATL static library substantially, so there are no longer multiple static libraries for debug/release mode or Unicode/ANSI character set. There is only one ATL static library that is common to all configurations.
The changes to ATL also included the elimination of the ATL/MFC Trace Tool and the simplification of the tracing mechanism. The TRACE macros now essentially boil down to OutputDebugString, and there is no external controller of tracing level (like the trace tool provided)—the tracing level is set in the application itself. This does cause source-breaking changes in some uses of the ATL::CTraceCategory class, which will require changes in source code when migrating to Visual Studio 2013.
The major change we made in MFC was the deprecation of MBCS support (see more information in this separate blog post).
In addition, we fixed about 105 bugs in MFC and about 60 bugs in ATL. About one-fourth of these bugs (in both libraries) were reported by customers.
Though I cannot provide a complete list of the bugs in our internal bug database, here is a list of the bugs that were reported by customers through our Connect site that have been fixed in ATL and MFC for Visual Studio 2013 RTM. Click on any Connect bug number to see more information about that bug. Note that most of these bugs were fixed for the Preview release as well.
atlbase.h disables no longer existing C4217 warning
Useless line of code in AtlSafeRealloc()
AtlSafeRealloc() treats failures inconsistently and this leads to memory leaks
CAtlServiceModuleT::LogEventEx() contains a useless check
Suspicious error handling code in CAtlExeModuleT::StartMonitor()
CComApartment::Apartment() leaks objects on edge cases
wrong/missing sal annotations on consumer oledb macros
Breaking change in how the ATL OLE DB CCommand::Execute method behaves
Certification fails for Windows Store App with ATL-based library
Uninstalling VS2012 Update 2 and repair of VS results in ATL files missing.
ATL CRBMap::Lookup code analysis markup issue
VC++11 regression: error C2338: db_command using v110 toolset
Static MFC executables produced by Visual Studio 2012 RC are huge
MFC loads DLLs using LoadLibraryEx with flag only supported on Windows8
CMFCRibbonBar::AddToTabs removes a wrong button from the m_arButtons array
EndDialog in OnInitDialog reopen Dialog
IMPLEMENT_DYNAMIC produces compile error for statically linked MFC projects
MFC Edit Browse box not showing browse button.
Calling EndDialog() within OnInitDialog() causes the dialog to be displayed twice.
Visual Studio 11 Beta – bug running .exe in XP service pack 3
Errors detected in the Visual C++ 2012 libraries
LocalFree called twice in CDatabase (MFC 11)
MFC OLE-Server doesn’t seem to support the new style MFC Toolbars
Attempting to use DrawStatusText after including afxwin.h results in link error
Probems with CRecordset::GetFieldValue(short nIndex, CDBVariant& varValue) in VS2012
x64 MFC Macro Bug – ON_WM_POWERBROADCAST() / CWnd::OnPowerBroadcast
CHttpFile::QueryInfo() returns “corrupted” CStrings with invalid lengths.
Missing MFC Functions
CWnd::GetScrollLimit returns 1 if scrolling is deactivated
CMFCPopupMenu crash when you click outside while submenu still open
CMFCShellTreeCtrl fails to handle some UNC pathnames correctly
MFC – CMFCTabCtrl – when style is STYLE_3D_VS2005 and SetActiveTabBoldFont() is set
Unpaired pragma warning push/pop in afxwin.h in Release build
MFC: bad hard typecast in CMFCToolBarMenuButton::CompareWith
HTTP_QUERY_FLAG_REQUEST_HEADERS on CHttpFile::QueryInfo() asserts wrongly
CMFCShellListCtrl::OnContextMenu ‘Delete’ context menu handler does not work
I hope you find this information useful. Please let us know if you have any questions.
Pat Brenner, Visual C++ Libraries Development Team