The MSIX Packaging Extension is an Azure DevOps extension which helps build, package and sign Windows apps using the MSIX package format.
CI/CD workflows have become an integral part of the develop...
Updated Feb 02, 2023
Version 3.0
Blog Post
Hi,
Following the documentation but getting stuck. Can't find anywhere to ask the question.
My msix worked perfectly fine on VS2019 on the desktop. Able to build msix and deploy and all that but all looks completely different on the web/azure pipeline. All the options are different.
I've been able to build a wpf project into $(build.artifactstagingdirectory) and deliver by azure pipelines into an artifact wpfdrop and deploy into a blob on an azure website. But you don't want people to copy a zip file to upgrade their files! Thought it would be simple to copy an msix into the blob instead and get the program to reference the website to upgrade whenever.
Without deleting any files, I've added "MSIX build and package" step straight after creating the wpfdrop. I assume all the executable file is still there. YAML equivalent code are:
steps:
- task: MSIX.msix-ci-automation-task.msix-packaging.MsixPackaging@1
displayName: 'MSIX build and package'
inputs:
outputPath: '$(build.artifactstagingdirectory)\TestProj.msixbundle'
buildSolution: false
inputDirectory: '$(build.artifactstagingdirectory)'
generateBundle: true
When I run it I get
##[error]No task definition found matching ID e8789f65-a0e2-472b-98ca-8cfd83ccc3c3 and version 1.0.0. You must register the task definition before uploading the package.
I thought the "MSIX build and package" is the task? What else do I need to do? I thought the task would pick up the executable in $(build.artifactstagingdirectory) and turn it into $(build.artifactstagingdirectory)\Winnet3.msixbundle ??
I could then 2) Sign it and 3) Create and App Installer after. Stuck on step 1) 😞
How do I register task definition? Can you point me to the documentation?