Learn about a framework that can be used to implement Visual Studio.NET-style Tear Off panes. The framework uses the commonly used MFC classes to achieve the functionality. This article is the fourth in the series.
This article discusses a framework that can be used to implement Visual Studio.NET-style Tear Off panes. The framework uses the commonly used MFC classes to achieve the functionality. This article is the third in the series.
Framework to build and use Visual Studio .NET-style Tear Off Panes
Framework to build and use Visual Studio .Net style Tear Off Panes
Enable your software to be provided with a professional and user-friendly interface with this MFC extension library, Professional User Interface Suite. (The article and demo project were updated.)
Position-interdependent popup windows have been used to great effect in current applications to simplify the organization of a complex UI. This article presents a flexible, if somewhat rustic, technique for accomplishing this behavior. (The source code was updated.)
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.
