I have problem with patches.
I have created a patch which should update installed soft.
My patch doesn't want to update (replace,merge...?) the file.
But if I manually delete this file then patch creates new (updated) version of the file.
Why does patch have such behaviour?
Also the problem could be because the version of your file is not changed between versions (from old package to the new package). So when windows installer verify the version thinks that your file is not changed.
We have encountered the exact same problem here- we've created patches (following the tutorials) and the patch does not want to actually do anything, unless the files to be updated are first deleted-- then the patch replaces the missing files with the correct ones. We've tried various suggestions found here and nothing seems to work. I'll have another opportunity to take a crack at it soon, and will send specific details about what we've tried, including the aip.
I have created a install (version 1.0) which installs properly.
and a udated install(version 2.0) which also works properly.
from these two msi files I create the patch file. which appears to work (it goes through all the motions) but afterward an investigation of the install directory reveals that none of the replacement or new files are in the directory.
I can provide all the aip and msi files that are needed to examine this problem.
Please tell me if you use synchronized folder. Because it was a bug in AI that cause to generate a new component for the synchronized folder with each refresh. The fix for this bug will be available in the next version of AI which is scheduled for release this week.
The workaround for this bug is to edit the AIP file of the new version and replace the GUID of the synchronized folder with the GUID of the synchronized folder from the old AIP file. Do this before you build the patch.
Also note that a in the case of files with the same name windows installer applies files Versioning Rules. To read more details about files Versioning Rules please see: http://msdn.microsoft.com/library/defau ... _rules.asp
If the problem persist could you please send both AIP files (version 1.0 and version 2.0) or a test AIP files that exhibits the same behavior to support at advancedinstaller dot com so I can take a look.
i have a version 2.00, then i changes the version of the program to 2.10, and i leave the APPDIR at the same spot on my HDD; only some added files is all...then i create a new MSI, then i do the patch, to check between the 2 MSI's 2.00 and 2.10..it does find 32files have changed correctly, the thing is, when i apply the patch, it doesn't overwrite the files!!! although the dates are newer 100%, fileversion, well, readme.txt .py(python) .xml(xml files) art files like jpg dds, etc...they dont upgrade, installed leaves the old in place
although the dates are newer 100%, fileversion, well, readme.txt .py(python) .xml(xml files) art files like jpg dds, etc...they dont upgrade, installed leaves the old in place
For non versioned files windows installer versifies the date modified to see if the file is newer or not. I test this and it works fine.
In order to investigate the problem could you please send both AIP files (if not contain any confidential informations) or a test AIP projects that exhibits the same behavior to support at advancedinstaller dot com.
I've been having major problems with the patch creation process. Updated installer files are created perfectly and all files are properly installed. However when I try to patch the software to delete unnecessary files/insert new files, the patch arbitrarily deletes files! It has become quite a problem since I have to send a patch every week to update my client's software.
investigating further, i've found the following problem:
base install 1.0 installs normally
Version 1.1 patch installs perfectly, adding the additional files.
Version 1.2 patch installs perfectly but deleting the files added in Version 1.1
Version 1.3 patch doesnt install because its looking for the files that were deleted in the Version 1.2 patch!
i was creating them between version 1.2 and 1.1. Is that correct? If it isnt then will i have to make separate patches for clients who have different base versions installed on their computers?
My patches are working fine now thanks to you. I appreciate the help.
I now have another query for which I'll have to give you a bit of background information.
My software is such that it warrants an update every week. In essence about 20 PDF files are updated each week on the software. In this way a total of 600 odd PDF files are updated in about a year.
My problem is simple - after my client gets his original installer file (lets say base version 1.1) he needs to update the software every week. The 20 odd files in every update have a cumulative size of around 400kb. The problem is that as the software keeps on getting updated week after week, the patches get larger and larger since the current image keeps on getting more and more different from the 1.1 image that my client has. Eventually, he will be downloading virtually 27MB just to update 400kb worth of files.
Is there a way around this? I would really appreciate it if you could help me out here.
The problem is that as the software keeps on getting updated week after week, the patches get larger and larger since the current image keeps on getting more and more different from the 1.1 image that my client has.
To avoid the patch to get larger and larger don't create cumulative patches. Create a patch between every two last versions (the target version needs to be installed). For example:
Create a patch between 1.1 and 1.2. To apply it version 1.1 needs to be installed.
Create a patch from 1.2 to 1.3. To apply it version 1.2 needs to be installed.
Create a patch from 1.3 to 1.4. To apply it version 1.3 needs to be installed.
So if you use the updater to update your application you can use the "Dependencies" feature. An update depends on other.
FOLLOW US
Get the latest news in Application Packaging