Auto update distribution with Patch?

[ngay528]

Previously in CVI, I created an auto-update feature that would automatically open the nidist.id file and checking what version was there to what was on the computers.  If it was out of date, I would open the setup.exe for the user.

The disadvantage with creating a brand new distributable is you have to include possibly enormous amounts of drivers for your program to work every time in case its the users first time installing your program.

However it sounds like the new "patch" system is suppose to solve this issue, however, the nidist.id file that is created contains the same version as the "base" version.

So, without adding a different file manually to check for an update is released, is there no way to detect that this "patch" is an update to the base version without including all drivers, especially when you changed one line of your code?

[Mert_A.]

If I understand correctly, you have implemented a sort of auto-update feature that will compare the currently installed version your application against the newest available version (perhaps on some network share), and then automatically launch the new installer if necessary.

You're correct that a patch installer has the same version as the "base" installer that it is patching. You might be able to use the file modified date of the two nidist.id files to determine if one of them is newer.

I can think of one other approach, but it is more of a drastic change. It sounds like you're thinking of having two distributions for your program available on some network share: the full one with drivers, for first time installations, and the patch, for updates to existing installations. Instead, you could have one distribution that only has the drivers, and another distribution that installs your full product. You would not use a patch-type distribution at all in this scenario. If you detect that the system needs a first-time install, you install both packages; otherwise, you use your existing version detection scheme to install only your application's package. Unless you have many files, or large files, in your application's installer, using a patch may not save you that much.

I hope one of these ideas may help you. If you have further questions, let me know.

Mert A.

National Instruments

[ngay528]

Thanks, both of those sound like viable options.  PS is the nidist.id file saved locally when installed, or do I need to save that modification date manually on first program start up?

[Mert_A.]

The nidist.id file is not saved/installed, but if you are already using the installer version exctracted from it, then I assume you must either be caching that file or the extracted version somewhere.

Mert A.

National Instruments