VB... brings up a good question: Do we continue to maintain two language versions of this? Having it in two languages made sense when it was an "illustrative example of how you can create your own adapters" -- but now that it is morphing into more of a "product" that may not be as important. I'd suggest one language, one version, one code-base. I'm all C# (I can do VB but prefer not to), so I'm biased. ;)