Patching immediately after full install does little

[MikeOnline]

I've built a compressed, web-based installer using InstallAware Studio Admin 7.01. I've also created a subsequent Patch for this install.

The Patch works properly most of the time; however, if I install the full installer, then install the patch immediately afterwards, only a handful of files are updated.

If I force the date of my computer to two days ago before installing the full installer, then set the date to today and install the patch, everything gets updated fine.

If I install the full installer and patch back-to-back without messing with dates, I notice my C# EXE's are getting updated, but my C++ EXE's and DLL's do not get updated. All of these EXE's and DLL's have properly constructed Version properties (e.g. File Version, et al) that are plainly visible in Windows Explorer.

I've made sure the full installer and the patch have the same Product Codes (GUID's), different Revision Codes (GUIDs), and different versions (the installer is 3.0.104.0 and the patch version number is 3.0.112.0). I've carefully configured Patches, Update Packs and Versions in my project, which consists of a single OFFLINE web media block. The project was based on a sample project included with IA Studio Admin, and keeps to the original flow of that sample.

I cannot figure out what I am doing wrong. Is any of this easier with InstallAware 8? Any other ideas?

- Mike

P.S. The Reset Date plug-in looks interesting, but only matches modification date to creation date, so I am not sure it would be any help. Besides, I am hoping to avoid having to mess with file modification dates, as I have two versions of these installers for locales other than the United States, which use alternate date formats.

[ulrichard]

hi Mike,

maybe the following two pages might provide some answers:
http://blogs.msdn.com/astebner/archive/ ... 58295.aspx
http://msdn.microsoft.com/en-us/library ... S.85).aspx

Rgds
Richard

[MikeOnline]

Thanks, Richard. The articles you mention explain why forcing the file modification date to the file creation date (via the Reset Date plug in) would make a difference when updating unversioned files.

I am still undure why some EXE's -- which ARE versioned -- wouldn't update, but I'll try running the Reset Date plug in and see if it helps. I'll post again once I have a resolution or new findings.

...UPDATE: things are going well now that I am using the Reset Date plugin for non-versioned files. Not sure why some EXE's weren't being updated, but I am building a newer patch that is working fine.

- Michael