Thread debugging can be one of the more difficult debugging exercises for a Visual C++ developer. The Visual Studio 2008 debugger contains a number of improvements that make thread debugging more productive, enabling code issues in multi-threaded applications to be identified and remedied faster.
Learn how to set up and use the Microsoft Symbol Server to help you debug applications under Windows.
While Visual Studio Team System cannot resolve the two intrinsic C++ unit-testing problems (cultural issues related to agile programming and lack of metadata in native C++), it does deliver a polished unit-testing framework for C++.
Debugger visualizers allow you to provide a custom user interface for the display of particular classes of data when your program is in debug mode. While there are some complex use cases for this, you can actually derive considerable benefit from very simple debugger visualizers—ones that take ten minutes or less to build.
An easy-to-use tool to find the description of various error codes, especially the ones returned by Platform SDK APIs, but also extendable for application-specific codes.
Debugging of code operating with mid-weight and heavy strings under Visual C++ is a real pain. Visual C++ native debugger has no cunning mechanism to show long strings. Of course, there are some debugger symbols like "s" and "su" which allow to see at most 252 symbols of string. But what about the rest?
The Transactional File System (TxF), which allows access to an NTFS file system to be conducted in a transacted manner through extensions to the Windows SDK API. MFC 10, has been extended to support TxF and related technologies. This support allows existing MFC applications to be easily extended to support kernel transactions.
The original release of the .NET Framework included collections as .NET was introduced to the Microsoft programming world. The .NET Framework 2.0 introduced generics to complement the System.Collections namespace and provide a more efficient and well performing option. Read on to learn more...
There are millions of Namespaces in the .NET Framework. Coming from a VB 6 background, I was accustomed to arrays and arrays only. Luckily all has changed with .NET, in that the .NET Framework supports Collections, which as its name implies, is a collection of objects that you can store in a certain manner.
WCF implementations normally take two different approaches; a Document style or an API style. Document style implementations are more flexible and often easier to extend and version. Also, Document style or rather, Message Contract service implementations, work well between systems with a shared message assembly. Jeffrey Juday guides you through architecting a WCF Message Contract implementation.
