InstallAware

Hi,
I've encountered some problems with my patch build. If I add only one new file to my installation sources, the patch build add several files that didn't change since the last build. The patch log file indicates:

INFO Comparing Files: R:\Produkte\xbound\500_Programme_released\SP_Test_1_V1\data\OFFLINE\B12386C1\D7B7F02F\xboundPluginContracts.dll v:\projekte\fox0001_int0077_valencia_stufe_1\500_entwicklung\520_setup\patchtest\sp_test_1\Patch\Upgraded Package\data\OFFLINE\B12386C1\D7B7F02F\xboundPluginContracts.dll...
INFO Comparing bytes...
INFO File Key: xbound7e17cxboundPlugInL344 is newly added"

for example. It seems to me that the patch lost his sequence after the new file occurs. Strangely, the new is file is not listed in the log file.

I've read the white papers, done a lot of tests, creates a fresh setup with small files and so on but I can't find out what the problem is.
I've also encountered this strange behavior if the script contains a "Set Environment Variable %PATH% to $TARGETDIR$\Bin" line that is included into the compiler variable "[compiler if Variable BUILDMODE not Equals PATCH]".

Any ideas? For now I'm not able to create patches and that is essential for a installer engine.
I forgot one (may be) important hint: The source is declared as "Install Files V:\Projekte\Setup\3.0.0\AlwaysInstall\*.* to $TARGETDIR$".
Could it be that there is a problem with the internal structure if I add a new file into the directory that is declared with *.* instead of declaring each file for itself?


Thanks,
Frank

Dear Frank,

It can definitely be that this is caused because you are using *.* and not specific files.
Furthermore, I would advise clearing your temp folders as well.

Hi Giaviv,
thanks for the prompt reply. I've done one more test with clearing temp folders and changing to specific files.
Clearing temp folder didn't change the behavior but save a lot of space (because of my massive test )
Changing to specific files did the trick. If I specify every single file, I can add a new file without causing the others.
Unfortunately, we have a lot of files in our deployment (around 300) and the process is designed to insert new file into this directory and the setup automatically gets these files.

From my point of view this is a bug. Is there a chance for fixing it?

Greetings
Frank

Dear Frank,

Its always nice to clear up space, isn't it?
I apologize for the inconvenience. This is not a bug, since the patch builder compares the changes of the actual files installed, by checking each Install Files command.

Hi,

OK, thank you for this clear statement.
I think that if InstallAware offers the possibility to use a mask like *.* then InstallAware has make shure that this works for patch builds as well.

We're working as an ISV and we always try to find solutions in the interest of our partners to.

Looking for an alternative now and thank you so far.

Best Regards
Frank

Thank you for your input, Frank!