Windows runtime dll's copied twice

When building a windows desktop project, 32-bit, I have to switch “Include runtime dll’s” on in order to run on some Windows 7 machines. No issue, this why we have this option. But, as I have had a year ago already with a previous version, now with 2017R3 I see again that the runtime dll’s as listed below are copied to the main exe-folder as well as the libs folder. This means we have them twice in the build folder, which is redundant and space consuming.
I am curious if anybody else has seen this behavior.

01-12-2017 20:19 19.136 api-ms-win-core-console-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-datetime-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-debug-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-errorhandling-l1-1-0.dll 01-12-2017 20:19 22.208 api-ms-win-core-file-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-file-l1-2-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-file-l2-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-handle-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-core-heap-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-core-interlocked-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-core-libraryloader-l1-1-0.dll 01-12-2017 20:19 21.184 api-ms-win-core-localization-l1-2-0.dll 01-12-2017 20:19 19.136 api-ms-win-core-memory-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-namedpipe-l1-1-0.dll 01-12-2017 20:19 19.648 api-ms-win-core-processenvironment-l1-1-0.dll 01-12-2017 20:19 20.672 api-ms-win-core-processthreads-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-core-processthreads-l1-1-1.dll 01-12-2017 20:19 18.112 api-ms-win-core-profile-l1-1-0.dll 01-12-2017 20:19 18.112 api-ms-win-core-rtlsupport-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-string-l1-1-0.dll 01-12-2017 20:19 20.672 api-ms-win-core-synch-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-core-synch-l1-2-0.dll 01-12-2017 20:19 19.648 api-ms-win-core-sysinfo-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-timezone-l1-1-0.dll 01-12-2017 20:19 18.624 api-ms-win-core-util-l1-1-0.dll 01-12-2017 20:19 19.648 api-ms-win-crt-conio-l1-1-0.dll 01-12-2017 20:19 22.720 api-ms-win-crt-convert-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-crt-environment-l1-1-0.dll 01-12-2017 20:19 20.672 api-ms-win-crt-filesystem-l1-1-0.dll 01-12-2017 20:19 19.648 api-ms-win-crt-heap-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-crt-locale-l1-1-0.dll 01-12-2017 20:19 29.376 api-ms-win-crt-math-l1-1-0.dll 01-12-2017 20:19 26.816 api-ms-win-crt-multibyte-l1-1-0.dll 01-12-2017 20:19 73.408 api-ms-win-crt-private-l1-1-0.dll 01-12-2017 20:19 19.648 api-ms-win-crt-process-l1-1-0.dll 01-12-2017 20:19 23.232 api-ms-win-crt-runtime-l1-1-0.dll 01-12-2017 20:19 24.768 api-ms-win-crt-stdio-l1-1-0.dll 01-12-2017 20:19 24.768 api-ms-win-crt-string-l1-1-0.dll 01-12-2017 20:19 21.184 api-ms-win-crt-time-l1-1-0.dll 01-12-2017 20:19 19.136 api-ms-win-crt-utility-l1-1-0.dll

Feedback case?

Joost,
I’ve just checked it and it doesn’t happen in my computer. (v. 2017r3)

I doubted since I had this a while ago and nobody, even the team, could reproduce it else then with my sample project, so they had to close the FB.

Thanks a lot for testing it for me Ramon.

Does not happen here. App made with X2017R3 on macOS for Windows 7+10.

Maybe it is just installing one version over older one?

I normally remove the existing buildfolder before compiling, just a habit.

Do you have your own CopyFiles build step that might be doing it?

Hi Tim, it’s not yesterday I started coding with Xojo … :slight_smile:

It’s not some funny with the target computers in the build settings, maybe ‘this computer’ and ‘Windows’? I don’t have a current license so I can’t test. ( Please excuse if silly idea ).