Modified Date changes for files on AI build

[versatile]

I noticed that when I was creating a patch file, that the modified dated was changing for some files that shouldn't have changed. The patch should only see 3 files changed, but it thinks there are 16 files changed. I went into the "cache" folders for both the original installation and the updated installation and I noticed in the updated installation, there were modified dates changed for files that should not have been changed. So when the patch was created, it thought there was a change in these files when there was not.

For instance, on my computer, the following file shows:

chrtnote.exe, modified date 9/18/12, file version: 12.9.25.1

When I view this file in AI in the "Files and Folders", it does show the same date and version as above. But after I build the installation and look in the cache folder, the file shows as:

chrtnote.exe, modified date 10/04/12, file version: 12.9.25.1

Which is today's date.

Why is this date changing when nothing has changed with the file? Just to let you know, it was working fine before I updated to your 9.5 version with one of my other versions. That is, between an original version and update version the patch worked and determined changed files correctly. But recently, you offered V9.5 and I updated to it. This forced me to create a new original version because of patch rules. I'm wondering if something might have changed in 9.5 that may be causing this issue.

Additional information: when I created the updated version, I did choose "Patch". I am on Windows 7 SP1 and as mentioned above I am using AI V9.5. I even tried removing the cache folder and rebuilt it which resulted in no change.

Thanks in advance for your help.
Ron

[versatile]

I'm sure I found the answer to my problem. In the properties of these files where the modified date is changing, I am having AI digitally sign them. That explains why the modified date is changing for these files. But, I'm trying to understand why it did not do this prior to the V9.5 update. For files that have a "File Version", it seemed it was only looking that the version and not the modified dates prior to 9.5. Now it seems to be looking at the modified date too when creating the patch by comparing the difference between the original install and the update install.

Is there a way to only look at the "File Version" for specific files and look at the modified date for files that have no "File Version"? That is, is there a way to specify this individually for each file, like in the properties? It seems like this property is needed for situations where the files are digitally signed by AI on install.

Thanks,
Ron

[Daniel]

Hello Ron,

Please keep in mind that this is the normal behavior when you digitally sign the related files. Also, can you tell us if you have enabled the "Digitally sign the file" option for the related file when you have built your project with an older version of Advanced Installer?

All the best,
Daniel

[versatile]

Daniel,

Thanks for the reply and sorry for not replying sooner. I was out of town.

Yes, all the settings were the same. I had enabled in Properties of each exe file to "Digitally sign the file". Did something change in this area as regards to the modified date?

I can understand that this is normal behavior in some cases. But, in the situation where the files are digitally signed, shouldn't the user be able to override this behavior and tell AI to only compare the versions and not the modified date? If we don't have this option, then every file that is digitally signed will always be flagged as modifed when compared for a patch build. Our software contains around 10 exe's, which would always be included in the patch even if they had not changed.

Thanks,
Ron

[Daniel]

Hello Ron,

I'm not sure why you have encountered the related behavior with versions of Advanced Installer lower than 9.5. Also, please keep in mind that this should be the normal behavior when you digitally sign a file.

All the best,
Daniel

[versatile]

Daniel,

I understand this is a normal behavior. But is there the possibility of a future update of adding a user option to be able to choose how the files are compared. Such as, for exe types it would compare version number only, whereas, other type files would compare modified date, version, and size of file. An option should be added in the patch build where all files would be compared as normal unless the user puts an exception in a list where they can type the name of files or use a wild card. Such as,

• Exception List:
  *.exe (compare version only)
  *.txt (compare size only)
  examplefile.eff (exclude all comparisons, do not compare)
  *.ptt (compare version and size only)
  
  All other files not listed in the exception list would would be compared as normal (created date, modified date, version, size)

It seems this option really needs to be added to the patch build or in the regular install builds to give the user more flexability on how files are compared. This way patch files will not be bloated with unnecessary files that have not changed.

Thanks,
Ron

[Daniel]

Hello Ron,

Currently for the diff operation, when creating patches, we use a Microsoft toll which is quite powerful. So, an improvement in this area now is improbable.

Thank you for your understanding.

All the best,
Daniel