I'm not completely sure i understand the other two issues.  Could you elaborate?

-mouser (July 01, 2008, 09:37 AM)

(2) Right clicking an entry and selecting recheck version does not seem to capture the installation of an update in the current dcUpdater instance.

Here is the scenario: I run dcUpdater and it tells me one package needs update. I select the option to update it, and it runs properly so the package is now up to date. If I now right click and select the 're-check version available on the web', it shows the currently installed version just the same as prior to performing the update. It seems that it might literally recheck the web version... but wouldn't it be sensible to also re-read the installed version data?

(3) It would be nice if when dcUpdater was launched by a specific .dcupdate file, that it could do a version check using the default list, and a right click option to add a .dcupdate file to the defaults if it isn't already there.

If I launch MyApp.dcupdate, dcUpdater starts and shows the details for MyApp, and only MyApp. It would be nice if there was a menu option to 'Check All' meaning to scan the default 'list' ($APPDATA\DonationCoder\DcUpdater\RedirectFiles) used by dcUpdater when it is started with no command line arguments.

The second part of (3) is that if a line item displayed is not in the default 'list' ($APPDATA\DonationCoder\DcUpdater\RedirectFiles), to add a right click option that allows the user to 'install' the MyApp to $APPDATA\DonationCoder\DcUpdater\RedirectFiles.

Does that make sense?

Owen

Some installers will not allow multiple concurrent instances.

It would be safer if DCUPDATER launched update processes one at a time.

Owen