How to package lots of standard functionality into a CListBox derived class.

A framework for system tray applets

The ATL OLE DB Provider templates only seem to support read-only rowsets and making them support updating of data isn't as easy as you'd expect!

The ATL OLE DB Provider templates only seem to support read-only rowsets and making them support updating of data isn't as easy as you'd expect!

ADO seems to be the ideal way to expose tabular data from your own COM objects and the ATL OLE DB Provider templates can help!

The ATL OLE DB Provider templates appear to rely on the fact that your data is kept in a simple array, but that's not really the case at all!

Adding bookmark functionality is relatively easy and it enables our ADO recordset to be used with a greater number of data bound controls.

A simplified method to enumerate a collection of objects.

This example COM component provides 3 COM objects for using the Win32 Mailslot IPC mechanism. The component may be useful if you need to communicate from VB using Mailslots.

COM objects can be categorised using the Component Category Manager. The code here makes it easier to use these categories in your code.

Using simple in-process COM objects you can make an application easy to extend without the need for recompilation of the main app.

There's no standard way to save complex COM+ application configuration in a form that can be placed under version control. This article presents 2 scripts that take advantage of the COM+ Catalog accessibility via script to provide functionality that should really come as standard.

Sometimes it would be nice to be able to use a simple C++ object as a sink for Connection Point notifications. This article shows you how.

A mini framework for writing Control Panel applets. Just fill in the blanks!.

Templates are a great way of reusing code, unfortunately MFC makes it hard to write MFC friendly template classes...

When a server has to deal with lots of short lived client connections it's advisable to use the Microsoft extension function for WinSock, AcceptEx(), to accept connections.

Writing a high performance server that runs on Windows NT and uses sockets to communicate with the outside world isn't that hard once you dig through the API references. What's more most of the code is common between all of the servers that you're likely to want to write.

To maintain performance a socket server shouldn't make blocking calls from its IO threads. This article builds on the previous one to add a business logic thread pool to our example server.

This article explains the potential problems with having multiple pending recvs calls on a single socket.

Although socket based TCP/IP servers using IO Completion Ports are often written in C++ it's sometimes useful to write such a server in Visual Basic.

When you're developing a TCP/IP server application it's easy to test it poorly. In this article we develop a test framework that does most of the hard work for you.

The Win32 Registry API is far too complex for simple tasks, and all the error checking gets in the way of the real work...