Unite the best features from the STL's basic_string and MFC's CString classes using an STL-based template string class. Allows all classes based on this template to be completely interactive with each other. (The article and source code were updated.)
Latest CString Alternatives Articles
CPerlString - A Class to Utilize Perl String Functions
String manipulation and regular expressions have always been a strength of Perl. Here are two classes that encapsulate some of Perl's most useful string functions for C++. (The source code was updated.)
ApxString - MFC CString Replacement
A non-MFC alternative to CString.
Simple String Class
Includes methods for formatting, searching (using wild cards) and numeric conversion to different data types
CString like class using STL
CString like class using STL
CUnicodeString Class
Updated source code!!
Latest Developer Videos
More...Latest CodeGuru Developer Columns
MFC Integration with the Windows Transactional File System (TxF)
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.
.NET Framework: Collections and Generics
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...

Working with Hashtables in .NET
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.
Implementing a WCF Message Contract
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.