5 replies to this topic

[ajeet]

This appears to be a MSI problem.

Upon a later versioned localized package product reinstall onto a non-English machine:

"msiexec.exe /i c:\myprod.msi REINSTALL=ALL REINSTALLMODE=vomus TRANSFORMS=c:\mytrans.mst"

it appears that the _old_ cached _transform_ is being used, not the new one - mytrans.mst.

Shouldn't the 'v' in the REINSTALLMODE tell the msi service to recache the transforms as well as the msi package ?

Any help or comments ?

- Ajeet

[ajeet]

This is a basic project, by the way.

Attached is the resulting patch MSI log.

Is anything obviously wrong?

Attached Files

•  patch.zip   14.81KB   43 downloads

[Stefan Krueger]

v will re-cache the.msi file. I didn't find any mention in the docs that this would also re-cache the .mst.
But this information may help you (although it needs a change already in the first version):

[comecme]

I hoped the 3.0 version of Windows Installer would also recache transforms, but it doesn't look like it does (at least not in beta 1).
The workaround of using embedded transforms does work, as does removing the current cached version of the transform, but both methods aren't what you'd want.

To me, it seems like something Microsoft simply forgot. There either should be a seperate option to recache the transform, of the use of v should recache the MSI as well as all of its transforms.

Does anybody know if this is supposed to be implemented in the final Installer 3.0?

[Glytzhkof]

So many things to remember, isn't there? Thanks for making this knowledge public. This should be a "best practice" recommendation "Always use embedded transforms". If I get some time one of these days, I will start writing all these loose ends up and make a FAQ of it.

[comecme]

I submitted this as an incident, but the reply the Installer Development Team gave me is that this works as designed.

IMHO, that would mean the design is incorrect.

There are no plans to change this in Installer 3.0.