Windows 7 DLL Conflicts

[ChrisW67]

IESHIMS.DLL shows as unresolved on every program I've ever run Depends.exe on. It is not the problem. The other one I've not seen before.

Are you sure you have the correct Qt DLLs in the path or application directory (searched first). Check that you have the files from the Qt you built and not the ones that Qt Creator was built with. You should also check release vs. debug Qt DLLs.

[eldecog]

I have exactly the same problem except that my program start but is really slow at start up.
With previous installation of Qt I remember my program started very quickly and it can take up to 10seconds to start!!
How can I solve this problem and speed up the starting process of my program? Because after start up, the program runs normally...
Thanks

[TorAn]

My experience:
I had a similar problem which I spent couple of days solving. It turned out that in the installation of the release build I accidentally included one of the qt dlls that was a leftover from 4.1. So, out of 5 Qt dlls I had 4 coming from 4.2 and 1 from 4.1. It caused my application to fail with the message (I can't recall exactly what was the message) that was cryptic enough that I had to check a lot of other things before I stambled accross the date of this offending dll. Onlly then I realized that it came to the release install from the times of 4.1. So, the advise it - ensure that alll qt dlls that are included in your release are from the same qt build and not from earlier qt releases.

Another issue was the bug in Qt (which I reported, it was accepted as a bug and the status is that it will be fixed in the future qt releases) is that QLibrary.fileName returns "dll" on Vista and "DLL" on Windows 7. So, if youi application does some manual loading you want to check this. The workaround is to convert the path to lower case prior to call "isLibrary".

Hopefully this information will be useful.