I would not post such a thing as this if I had not spent a LOT of time looking at it.  But I have, and the new Application Updater Block v2.0 has been neither easy to implement nor reliable in even toy problems for me.  I'm extremely disappointed.  I understand that I probably don't understand properly how to use it.  But I also know I'm from from an idiot and walking through the step-by-step instructions and QuickStarts multiple times should have made it relatively easy to implement an out-of-the box auto-update.  Not the case.

I've googled. I've followed the help instructions. I've modeled the QuickStarts.  I've Uninstalled and reinstalled.  Recompiled the AppBlocks and Ent. Library using some of the various different build configs (why does Release compile but ReleaseFinal does not??).  Regardless of these efforts I have had to step into code everywhere just to figure out that my trivial updates weren't downloaded by the BitsDownloader or why my error events weren't firing when Bits encountered a COM exception etc. etc.

I know a lot of brilliant people worked on this thing, and I know it's highly configurable and extensible (or is supposed to be).  But like with most generic purpose, complex things, it's NOT easy to use and does require specialized knowledge of its inner workings in even the most basic case of true end-to-end auto updates.  If anyone wants to step up and point me to (or write!) a no-fail guide to a simple vanilla implementation of AUB2.0 with a Windows app I'll be grateful.  But I won't believe it's simple or easy when I have, with great humilty and focus tried to implement auto update with it several times and faced non-trivial roadblocks at each one.