Hi,
I'm not actively developing DDay.Update currently, but our business uses it in nearly all of its projects, so I plan on making additions/changes as time goes on. In reality, there aren't a lot of alternatives out there, which is why I undertook developing DDay.Update in the first place.
I've used the .NET Application Updater Component on previous projects, and found it lacking in many ways. I had enough problems with it that I starting looking elsewhere, and found ClickOnce to be a fair improvement on its own merit. At the end of the day, ClickOnce was still overly tedious to customize, and had some pitfalls of its own (as any solution will), so DDay.Update was born with the goals of customization and ease-of-implementation.
Proxy support isn't quite there yet, but I've had requests for it, and even had a patch submitted (which unfortunately can't be used as-is). It should be somewhat simple to add, and I'd like to provide support for this soon. The company where I'm employed has some major projects coming up that will heavily rely on DDay.Update, so I imagine I'll be working on it much more within the next couple of months.
Hope that helps.
Regards,
-Doug