Collections are a vital element of any object-oriented architecture. This article, by Luther Stanton of Intellinet Corporation, introduces collections, looks at some of the benefits and potential drawbacks of using custom collections versus built-in collection-like elements, and then provides a discussion of interfaces and implementations.
Curious about what to expect in 2005 out of the development community? Check out Bradley Jones' yearly forecast on what to anticipate.
Explains the programming paradigm (including type safety and performance) used within the .NET Framework Base Class Library (BCL) for enumerating objects.
Illustrates how the .NET Framework offers a consistent programming paradigm for working with collections, lists, and dictionaries.
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...
The final installment of our Slot Game series shows you how to build in a way to win or lose. We will also add some effects for when a win takes place.
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.
