Hi,
I am wondering if the UAB is the right approach for my problem.  I need to
create an updater application that keeps track for any possible updates for a
given list of applications. Similar to "windows update" service though for my
custom applications :-)
Based on the msdn information and the quickstarts it seems like a possible
solutions could look like the following:
* Have one major manifest file for each sequence of updates, version 1,2,2.1
etc.   i.e. includes several other manifest files that includes the updates
(exe,msi files) for my other applications.

* Create a windows service , called "updater app" based on uab 2.0
* Point out the major manifest file in my app.config.
* Somehow initiate the download and start activation process
* Note: Include in download even a new app.config reference
(updaterconfiguration.config) to next version of manifest file so the
"updater app" will point out the next sequence of updates , this needed based
on fact that the server should have several versions of updates simultaneous.

Q: So much in theori, should i proceed in implementation of this OR  is UAB
ment for something else and there a better approach to my problem.
Any idéas? What is the best practise for UAB?

Thanks for any information / help in advance.