Forum Discussion

Copper Contributor

Feb 25, 2021

Solved

Create MSIX Package in Release Pipeline!

Hello, I'm new to UWP development and CI/CD pipeline. I'm trying to create MSIX using UWP project. Below are the scenarios where things work and what I'm looking for. 1. I'm able to generate MS...

Chacon
Mar 02, 2021
Hi s_salaria

The AppxManifest.xml should be in the root of the directory you are packaging. So you need to either move it to the BRMS_Packaging_MSIX\Shell\ directory or point the task to the BRMS_Packaging_MSIX\ directory. (Which probably means that the task doesn't actually need to ask for the path to the manifest, or that if it does it should be using it even if it's not at the root.)

In your manifest file I noticed that there is a reference to a Shell\*.exe file and several Images\*.png files. These files must exist relative to the input directory, so you will want the directory you pass to the task to look something like this:

\ AppxManifest.xml Shell\ BRMSv2.exe ... Images\ StoreLogo.png ...

s_salaria

Copper Contributor

Mar 01, 2021

Hi Chacon,

Thank you for your response. How I can create MSIX package in release pipeline because task "MSIX build and package" look for .sln which is not present in Artifacts(build output). Artifact contains build output(dlls and config file) or msix package(if I include packaging information in vsbuild arguments).

Is there a way to create MSIX in release pipeline?

Chacon

Microsoft

Mar 01, 2021

In the "MSIX build and package" task, un-select the option "Build solution with MSBuild". Then instead of pointing it to the .sln you will have to point it to the directory containing the contents of the package (like dlls, config and assets) which you already built.

This directory also needs to have an AppxManifest.xml. You could create this by hand, but I believe the VSBuild task should already be creating it for you from the Package.appxmanifest file.

s_salaria
Copper Contributor
Mar 01, 2021
Thank you,

I'm trying the things in same direction as you suggested. Below are the Artifacts copied by build pipeline.

Below are the settings in release pipeline(Packaging).

but I'm getting below error during packing task
- Chacon
  Microsoft
  Mar 01, 2021
  s_salaria ,
  
  Are you trying to create an MSIX package or an MSIX bundle? Sorry, I just assumed you wanted a single package before. You can see a bit more about bundles here: Bundling MSIX packages - MSIX | Microsoft Docs
  
  If you are trying to create a single package, you need to un-select the option "Generate MSIX Bundle". If you select that option, the task will expect a directory containing the multiple .msix packages from which it will create an .msixbundle. If you don't select it, it will expect a directory with binaries, assets and an AppxManifest.xml to create an .msix. The error comes from selecting to produce an MSIX bundle, but using a directory with loose files.
  - s_salaria
    Copper Contributor
    Mar 02, 2021
    Hi Chacon,
    
    I've changed all the setting as per your suggestion but still I'm getting error "
    MakeAppx : error: You must include a valid app package manifest file named AppxManifest.xml in the source." I'm browsing AppxManifest.xml from artifacts.
    
    Can you take a look in below settings and suggest what I'm doing wrong:
    1. Build task(.yml)
    
    2. Output in Artifacts. Shell is the actual .csproj referenced in UWP project
    
    3. Release pipeline task settings
    
    4. Appxmanifest.xml in Artifacts