What order should the OK and Cancel buttons appear? Should it be like Windows or like the Mac? Are there any "rule of thumb" as to when certain standard should be followed or is it just a matter of taste?
Discover a very simple, integrated method to make a control, such as static, button, sliderctrl, and progress control transparent in a dialog box.
Learn more about this very useful library.
Learn how to build an efficient library to provide support for Message Only Windows. The article also shows how to use the Thunk32 library provided in an earlier article, as well as some general pointers on good practices and patterns.
BiSplitter is MFC-compatible class for creating a splitter window that looks like a Microsoft Outlook window.
The dynamic screen classes allow you to incorporate advanced screen functionality into your MFC applications. The fundamental difference of these classes are that they work with the actual resource in your executable—this means that users of your applications can alter screens that have been designed by you using the MFC resource editor—they can make changes at run time.
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.
