I made some more progress with the code updates today.  The basic USB demo code package is now updated, you can download it in its respective article.  The code is now reduced to a much simpler interface with the packaged DLL which handles all the 'dirty work' of the USB routines.  The code package for the DLL is also available for separate download.

Today I spent quite a lot of time updating the USB bootloader code.  It started out as a simple upgrade to use the DLL, which would have taken minutes, but wound up being a long project because I was fed up with the way the program was structured - from the programmer's standpoint, there were three separate classes that needed to be dealt with, and all the multi-threaded functionality of the more advanced code was implemented in the "user code" in the form, so to speak.  I realize that this probably made it pretty hard for others to figure out the codeI have drastically restructured it all so that all of the functionality is encapsulated in a single class, with only a few easy-to-use methods to deal with from the user's standpoint.  The code in the form itself no longer has to do any of the hard work, making the bootloader a lot less painless to use from a programming standpoint.  I still need to spend some time cleaning things up and adding comments throughout, but everything appears to be workable at this point at least.  I haven't entirely decided yet if I want to release the bootloader code as another DLL that extends the core code in my other one, or add it right into the other DLL, or something else entirely.  I'll try to get it all updated in the next few days

Next (and final) step is for me to get the code for the asynchronous transfers article revised.

I have been toying around with programs that will auto-generate help files from the XML commenting in the code.  This would produce documentation of all the classes, methods, events, etc. similar to what you'd see on MSDN, et al.  Once I've got all the 'real' stuff done I hope to get something like this working so I can generate some more substantial documentation so that my code is easier to use.