3 replies to this topic

[mikemio]

Hi,

I have a package with a third party dll version 9.60. The dll has a bug and I must revert to version 9.10.

I prepared a minor update with the older dll and , not too surprisingly, it did not work. The odd thing is that it does work after one 'repair' (but of course that is not acceptable).

My question is what is the best way to do this? Could I create a false version in the msi file (say 9.61 which I know will never be used) or would that just create a mess later on.

I am using VS2005 to build the msi file and the dll is in a merge module.

Thanks in advance for any suggestions you may have.

Cheers,
Mike

[Stefan Krueger]

The best way would be to increment the version of the DLL itself. Version lying in the msi database is not ideal but doable. The clean way would be to uninstall the buggy version.

[mikemio]

Thanks Stefan,

The dll source is not under my control. I could increment its version in the file I suppose but I can't be sure that would not have any side effects in its operation.

When you say the clean way it to uninstall the buggy version, isn't that what happens with an update? That is, I thought that an update (made with VS2005) runs the uninstall of the previous version silently and then runs the newer installation. Then again, I guess if that where true I wouldn't have this problem.

I wonder is RemoveFile would be an option to remove the buggy dll? As I understand it, that is run before the files are installed.

Anyway, worst case I will go with the false version number.

I really appreciate you sharing your insights.

Cheers,
Mike

[VBScab]