Replies: 1 comment
-
There is not enough detail here to really be useful. You might start by providing much more detail about each step you've done and what you see with the patch applied and not applied in Orca. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I am trying to create an MSP using pure Wix method. I am facing an issue because of renaming functionality in my MSI. Below is my MSI code.
We extract the OS culture and use it within the condition, and copy the appropriate localization dlls. Renaming is also done after copying (to LanguageFile.dll)
I have similar MSI's for both RTM and Hot Fix, the only difference is that, HF MSI has new dll versions.
Steps executed to create MSP:
Ran the msiexec for both RTM and HF msi, and fed the resultant files to Torch.exe command (MSI and extracted files)
Then executed Candle.exe, Light.exe and Pyro.exe commands to create an MSP
When we run the HF5 on an English OS, observed that EnglishComponent was picked up but wrong file was copied i.e. French localization file with name LanguageFile.dll
Assuming this happened because, while running exec step, it first copied English dll with name LanguageFile.dll and then French dll (renamed to LanguageFile.dll after copy - overwriting existing English dll) Then, the French language dll (with name is LanguageFile.dll) is mapped to all the components (EnglishComponent and FrenchComponent)
Beta Was this translation helpful? Give feedback.
All reactions