Apart from Hashtables, queues and stacks are probably the most common Collection classes. This article explains the ins and outs of queues and stacks.

Apart from Hashtables, queues and stacks are probably the most common Collection classes. This article explains the ins and outs of queues and stacks.
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.
For some reason, setting file associations is still somewhat of a mystery to many a developer. Hannes du Preez shows you how to create an installer package to do it for you!
This is the last installment of Creating your own Hidden Object game with VB.NET shows you how to add a Hint Facility, how to change screen resolution, and how to finalize the game.
As we continue our walk-through on how to create a hidden object game, the discussion turns to adding functionality to the project that will produce a working game.
Learn how to make your own hidden object game. Hannes Du Preez walks you through creation and describes the logic involved with these types of games.
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...
Apart from Hashtables, queues and stacks are probably the most common Collection classes. This article explains the ins and outs of queues and stacks.
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.