Deployed MAUI app as MSIX on server 2019 not unpackage

[danies8]

Description

Deployed MAUI app as MSIX on server 2019 not unpackage

Steps to Reproduce

1.Create MAUI app.
2.Deplayed as msix.
3.Not worked on server 2019.

Link to public reproduction project repository

..

Version with bug

Unknown/Other (please specify)

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

..

Did you find any workaround?

..

Relevant log output

..

VS bug #1814061

[ghost]

Hi @danies8. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[ghost]

Hi @danies8. We have added the "s/needs-repro" label to this issue, which indicates that we require steps and sample code to reproduce the issue before we can take further action. Please try to create a minimal sample project/solution or code samples which reproduce the issue, ideally as a GitHub repo that we can clone. See more details about creating repros here: https://github.com/dotnet/maui/blob/main/.github/repro.md

This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[danies8]

This the command I used:
msbuild /t:restore AutomationClient.MAUI.csproj
msbuild /t:Publish AutomationClient.MAUI.csproj /p:TargetFramework=net6.0-windows10.0.19041.0 /p:configuration=release /p:GenerateAppxPackageOnBuild=true /p:AppxPackageSigningEnabled=true /p:PackageCertificateThumbprint="c01ba45666762f3615cf6813aeb4dc4b1919541d" /p:PublishSingleFile=true

[danies8]

Moreover, as a developer must carefully consider everything that normally comes with the MSIX package and ensure they're available in the target environment. Publishing self-contained just means the .NET runtime, it doesn't mean it will automatically check to see if fonts are installed or other things. When unpackaged, we are responsible for making sure all resources, like custom fonts, must be in the operating system environment when that unpackaged app is run. If you are not sure what those things are, you can change ".msix" to ".zip" and extract it to see the contents.
Can you also fix these problems?

[danies8]

1.Put all files in C volume.

2.You will need to have the Desktop Experience installed as well as any dependencies for your app
(.Net Framework, Windows App SDK, etc.) that aren't included by default in Server 2019.
See https://docs.microsoft.com/en-us/windows/msix/msix-server-2019
3. NET runtime - See link https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.7-windows-x64-installer
4. NET Framework - See link https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-web-installer
5.Install latest see link Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle(https://github.com/microsoft/winget-cli/releases/download/v1.3.1872/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle)
via powershell Add-AppxProvisionedPackage -Online -PackagePath C:\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle -LicensePath C:\a941c144deac426082dc9f208f729138_License1.xml -Verbose
(XML can be found here in this link: https://github.com/microsoft/winget-cli/releases/download/v1.3.1872/a941c144deac426082dc9f208f729138_License1.xml
6.VCLibs - the files located in this link https://docs.microsoft.com/en-us/troubleshoot/developer/visualstudio/cpp/libraries/c-runtime-packages-desktop-bridge#how-to-install-and-update-desktop-framework-packages.
Install the x86 and x64 appx files with Add-AppxPackag(https://docs.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2019-ps#description=)
The commands are:
Add-AppxPackage -Path "C:\Microsoft.VCLibs.x64.14.00.Desktop.appx"
Add-AppxPackage -Path "C:\Microsoft.VCLibs.x86.14.00.Desktop.appx"
The results blank window.

[PureWeen]

@danies8 does this look related?

microsoft/WindowsAppSDK#2829

[ghost]

Hi @danies8. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[danies8]

@PureWeen I read #2829 I list what I installed in server 2019. Do I need to install something more?
If yes please specify link where I can install this ?

[danies8]

@PureWeen
Do I need to install https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads
Version 1.1 3 files c#& c++ extension and x64 installer?

[mattleibow]

The story with MSIX is that all the requirements and dependencies should be installed with the app.

If you create a plain WinUI app, does it also have issues?

Also, the publish with /p:PublishSingleFile=true might be an issue as this is not relevant.

And, /p:GenerateAppxPackageOnBuild=true should not be needed when publishing.

Is there a difference when you use dotnet publish -f net6.0-windows10.0.19041.0 -c Release /p:AppxPackageSigningEnabled=true /p:PackageCertificateThumbprint="c01ba45666762f3615cf6813aeb4dc4b1919541d"

[ghost]

Hi @danies8. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[danies8]

I used tis code:
dotnet publish -f net6.0-windows10.0.19041.0 -c Release /p:AppxPackageSigningEnabled=true /p:PackageCertificateThumbprint="c01ba45666762f3615cf6813aeb4dc4b1919541d"
and it work on window 10 but not work on server 2019, i get blank window

[danies8]

@mattleibow can you please say what to do?

[mattleibow]

This issue was moved to microsoft/WindowsAppSDK#3020