Windows App Certification issues

[jasoncd]

I'm working on replacing our MSI projects with new MSIX projects created from scratch. When running the Windows App Certification kit, I receive several errors. First, is it possible to disable or remove the stub exe files? This is a basic installer and shouldn't need a stub. I also get the following errors:

File AI_STUBS\AiStubX64.exe contains a reference to a "Launch Process" related API kernel32.dll!CreateProcessW
File AI_STUBS\AiStubX64.exe contains a reference to a "Launch Process" related API shell32.dll!ShellExecuteExW
File AiStubX64.exe contains a blocked executable reference to "\WindowsPowerShell\v1.0\PowerShell.exe".
File AiStubX64.exe contains a blocked executable reference to "PowerShell".
File AiStubX64.exe contains a blocked executable reference to "Powershell.exe".
File AiStubX64.exe contains a blocked executable reference to "cmd".

I realize the MS Store might not object, but I don't need it anyway. It would also reduce the risk of false positives from virus scanners.

I also have errors regarding image assets, but only when using a bundle. A standalone MSIX does not generate these errors. I receive these for several resolutions.

Image reference "Assets\VetaSquare44x44Logo.png": The image "Assets\VetaSquare44x44Logo.targetsize-16.png" is missing from the package.
Image reference "Assets\VetaSquare44x44Logo.png": The image "Assets\VetaSquare44x44Logo.targetsize-16_altform-unplated.png" is missing from the package.
The "[snip].Veta_8.0.34.0_neutral_split.assets_fmsq6gs70gyqy\resources.pri" file is missing, and it must be present in the bundle for this resource package.
Manifest Resource Validation Test encountered error: hr = 0x80070002.

[Liviu]

Hello,

First, is it possible to disable or remove the stub exe files?

Unfortunately, this is not possible. And this is because if you would do so then your application may not work properly when running under the MSI container.

The AiStub.exe fixup module is used by us to add Package Support Framework capabilities to your MSIX package. And some of the Package Support Framework capabilities and functionalities (e.g. files and folder redirections) are inserted automatically and silent by Advanced Installer into your MSIX package at build time.

If the AiStub.exe is included automatically by Advanced Installer in your MSIX build this means that Advanced Installer detected that your application needs some fixup capabilities to run properly in the MSIX container.

So I would not advise you to try removing the AiStub.exe module from your MSIX package.

I also get the following errors:

File AI_STUBS\AiStubX64.exe contains a reference to a "Launch Process" related API kernel32.dll!CreateProcessW
File AI_STUBS\AiStubX64.exe contains a reference to a "Launch Process" related API shell32.dll!ShellExecuteExW
File AiStubX64.exe contains a blocked executable reference to "\WindowsPowerShell\v1.0\PowerShell.exe".
File AiStubX64.exe contains a blocked executable reference to "PowerShell".
File AiStubX64.exe contains a blocked executable reference to "Powershell.exe".
File AiStubX64.exe contains a blocked executable reference to "cmd".

I realize the MS Store might not object, but I don't need it anyway. It would also reduce the risk of false positives from virus scanners.

Can you please give us more details about this or a test case which I can follow in order to reproduce this problem?

I also have errors regarding image assets, but only when using a bundle.

and also a test case for this problem too.

Best regards,
Liviu

[jasoncd]

Ah, I see. That is helpful. I experimented with my installation settings and was able to prevent the need for the stub to be used. Still learning about MSIX... I'll continue testing and see if I can get the image issues to go away. I may just recreate the project.

[Liviu]

Hello,

If you can not get this working, then you can forward to us your .AIP project file by email to support at advancedinstaller dot com and a test case which we can follow in order to reproduce this issue.

Best regards,
Liviu

[jasoncd]

I have not figured out yet what is triggering the resources.pri error in WACK. However, our app was accepted by the MS Store, so I won't dwell on it.

The image issue seems to be this:
https://stackoverflow.com/questions/150 ... er-warning

"targetsize" and "scale" should not be mixed. However, MS documentation seems to say you need everything. Indeed, if I remove the "scale" images, there is no error. I think maybe the WACK tool shouldn't be trusted sometimes. Everything seems to actually work, though, so I won't lose sleep over it.

[Liviu]

Hello,

Thank you for your follow-up on this.

Please let us know if you have any other questions.

Best regards,
Liviu