Page 1 of 1

NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Tue Feb 28, 2017 10:56 am
by mikKummerfeld
Hello Support,

we are using native_engine and NATIVE_OVERWRITE is set to ALWAYS and NATIVE_OVERWRITE_OLDER is set to TRUE.

Why do we get this PROMPT-Dialog while installing:

overwrite.png
overwrite.png (14.61 KiB) Viewed 9454 times

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Tue Feb 28, 2017 12:28 pm
by FrancescoT
Dear heiko,

does it happen when the installer tries to overwrite a file that is newer with an older copy?

Regards

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Tue Feb 28, 2017 12:30 pm
by mikKummerfeld
The installer has newer files inside than the installed ones.

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Tue Feb 28, 2017 12:41 pm
by FrancescoT
I'll check this out and I'll let you know.

Regards

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Thu Mar 02, 2017 6:01 am
by FrancescoT
Dear Heiko,

I don't see any problem with setting NATIVE_OVERWRITE = ALWAYS and NATIVE_OVERWRITE_OLDER = TRUE.

I used a simple project to test the "Runtime" behavior of these variables and the native setup engine doesn't display any "overwrite dialog" when replacing an older/newer file.

If you want to check by yourself, you can used the attached test project.

To test the "NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER" behaviors;

First test!
- Build the project and then run the "test.exe" on a target machine.
- Once installed, update the "document.txt" under; "C:\Program Files (x86)\test"
- Re-run the "test.exe" and select to repair the installation.
Result > the "document.txt" gets replaced without displaying any "overwrite dialog".

Second test!
- Keep the "Test" package installed on your target machine.
- update the "document.txt" under; "C:\Program Files (x86)\test"
- Re-Build the project and then and run the new generated "test.exe" on the target machine.
Result > the "document.txt" gets replaced without displaying any "overwrite dialog".


PS!
It's not necessary to change the location of the project source files ...I used relative paths.

Hope this helps you.

Regards

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Wed Mar 08, 2017 8:47 am
by mikKummerfeld
Franseco our customers are very angry. How can I avoid the overvwrite box ?
That is my only question :)

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Wed Mar 08, 2017 10:59 am
by FrancescoT
Dear Heiko,

I am very sorry for your customers, but I don't see any problem with the NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER variables.
For me these work as expected.

Did you have a look at the sample I posted previously? ...it seems you didn't.

Regards

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Wed Mar 08, 2017 11:57 am
by mikKummerfeld
I know what is different :) The existing file is not a file on target system. With native_engine there is a problem with

command "Install files" when you have the same file in different source folders but you need to install them in the same destination folder.

e.g

install files from ..\..\files\*.* to dest folder => source dir contains readme.txt
install files from ..\..\files2\*.* to dest folder => source dir also contains readme.txt

then the messagebox appears

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Wed Mar 08, 2017 12:07 pm
by FrancescoT
...but if it's just this the problem, you may use a different name for one of these "readme.txt" files or you may skip to include one of them.

Regards

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Thu Dec 07, 2017 6:26 am
by mikKummerfeld
it is not possible to rename or exclude because we have hundreds of dll files in 2 source directories and if we install both applications we have that copy problem. We would like to buy X7 but if the bug stilll exists...we can not

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Thu Dec 07, 2017 2:11 pm
by FrancescoT
It'll be very hard to fix something, which works as expected and it's not a bug either.

Regards

Re: NATIVE_OVERWRITE / NATIVE_OVERWRITE_OLDER

Posted: Fri Dec 08, 2017 9:50 am
by mikKummerfeld
It does only happen with native engine. Without it works fine.