Windows Sockets: Converting Strings
The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.
The latest version of this topic can be found at Windows Sockets: Converting Strings.
This article and two companion articles explain several issues in Windows Sockets programming. This article covers converting strings. The other issues are covered in Windows Sockets: Blocking and Windows Sockets: Byte Ordering.
If you use or derive from class CAsyncSocket, you will need to manage these issues yourself. If you use or derive from class CSocket, MFC manages them for you.
Converting Strings
If you communicate between applications that use strings stored in different wide-character formats, such as Unicode or multibyte character sets (MBCS), or between one of these and an application using ANSI character strings, you must manage the conversions yourself under CAsyncSocket. The CArchive object used with a CSocket object manages this conversion for you through the capabilities of class CString. For more information, see the Windows Sockets specification, located in the Windows SDK.
For more information, see: