My confusion here came because we really want the full installer to be a web install as well. 1.5GB of compressed data does not translate well to a single-file download.Quote:
How would I enable Web Update in the full install to refer to the update installer?
The answer I was looking for is: Both the full installer and the update must have the same [EXENAME]. They should both refer to the same update location. But they should be accessed using two different URLs.
I think that for now we'll do the simplest thing, maintaining a single installation project and adding Delete File commands manually as necessary.
If you add file deletion to AutoUpdate, we will consider the 2-project method. I'm still concerned about the case where version 2 adds some files and version 3 deletes them. If a user with version 2 applies the AutoUpdate that was generated using version 1 and 3, those files will be orphaned. This is of course better than the situation now where all deleted files get orphaned.
Ideally, file deletion would be taken care of automatically using a single installation project. Does SetupBuilder not store a list of installed files?