I have a legacy win32 application which I tried converting using the DAC providing the .msi from the application installer and the application works as is post conversion. But I have few queries below.
- I used the same Base Image as my OS version for the conversion. But the converted application isn't launching on RS1 and RS2 OS images. It throws below error.
"This application was unable to start correctly (0xc0000142). Click OK to close the application."
- My legacy application Installer has both Setup.exe as well as .msi file in the installation package. The setup exe only has language selection feature. Based on the user selection particular .mst file is passed as parameter to msi and launched.
Now while converting my desktop app, should I generate multiple appx files by providing all language .mst filenames as parameters to the .msi while conversion?
How to handle the above scenario so that my converted app should launch in that particular language based on the OS?
Also while appx installation can App Installer show in that OS language? How to support that in this converted application scenario?
1) Of the top of my head, maybe you're missing dependencies like some VC++ redist?
2) The conversion process will only capture the language used to install the application, i.e. the one you specify in the command line. It cannot detect and include all the languages, even if your MSTs are present.
From what I know the AppInstaller for appx/msix packages cannot display a language selection dialog, this is all handled by the OS, transparent for the end-users.
If you plan to build a package with resources for multiple languages you need to use MakePri. Check the linked thread for an example.
Also, another great example on using MakePri.