Hi Luis,
So far as I know, you would have to write your own. That is what we did at my shop.
Each of our applications has an entry in the database which is linked to using the application's AppName property. Among other things, the database stores the names of the application's files. Upon launch, the application compares the file dates of its files on the local disk where it is running with the files in the central repository. If any of the local files are older than those in the central repository, it initiates the application synchronize function.
The synchronize function constructs an INI file that includes the app path of the app to be updated as well as paths to each of its files and the corresponding file in the central repository. This information is all drawn from the application's database entry. The application then launches an update application and quits.
The update application uses the information from the generated INI to update all the requisite application files, and then re-launch the application once the files have been updated, and having re-launched the application, it quits.
You need Windows API to compare file dates (FindFirstFile, FindClose, CompareFileTime functions), and is heavily dependent upon the environment in which you are running your applications. In our case, we have had a very stable, well controlled environment and our process works extremely well for us. The process is a bit cumbersome, but it can be done once and forgotten about. We put it in place somewhere in the 1999-2000 timeframe and have really not done much to it since.
Andy