InstallAware

How can I tell the install to check the web first for a webblock and if not found take it from the disk.

Of Is there a concept of an optional webblock that if not available it wont give an error message?

-- Robert Kozak

The opposite is automatic - check on disk, then check the web. You cannot make them optional.

MichaelNesmith wrote:The opposite is automatic - check on disk, then check the web. You cannot make them optional.

Doesn't this sound backwards considering that items on the disk would be older than what is on the web?

We do releases about once a month but create disks only a couple of times a year. After a month or two our installs are already out of date. WebBlocks are a great idea but would be perfect if they check the web first because it would be the most up to date. If there is no web blocks on the web then that means the disk version is the latest.

Failing that I tried creating a webblock "DiskOnly" that contained all our required files and then another WebBlock "Web" which we wouldn't put on the disk. Unfortunately if the enduser installing the product doesn't have an internet connection it fails because it *REQUIRES* the web block "Web" which it doesn't really need.

Are you saying that it is technically impossible to make a webblock obsolete or that InstallAware has no interest in making them optional?

-- Robert Kozak

Technically you must update the MSI database that accompanies the weblock, every time the weblock contents change. Otherwise the MSI will fall out of sync with the weblocks. This is why the older version of the weblock takes precedence and an alternative is not available.

Thanks for the explanation. Its a shame though.

Does this also mean I really shouldn't change the contents of a webblock?

Example :
I create a Web Block A: with one file File1.exe

Place the install on the disk without Web Block A which I put on our download server. Then later (week or so) update the install and Add a File2.dll to Web Block A and replace the Web Block A on the download server.

Will this cause a problem?

-- Robert Kozak

Adding files will not cause a problem, changing existing files won't either, as long as they are not part of the file references in the MSI database (ex: prereqs, custom MSIcode commands that aren't put into the MSI, and so on).