Hi, nice video. I also had tried ADO for my MAUI pipelines, but instead of the bash task, I simply use the DotNetCoreCLI task to install the workloads and build the different files for Android, iOS, ...
I see the .msix file does get created during the build, but unforutnately the --output parameter does not copy it to our output folder. I'd suggest performing the build locally to see the file structure of the output. You'll find the msix file in a directory similar to: MauiPipelinesDemo\MauiPipelinesDemo\bin\Release et8.0-windows10.0.19041.0\win10-x64\AppPackages\MauiPipelinesDemo_1.0.0.1_Test\MauiPipelinesDemo_1.0.0.1_x64.msix. You should be able to copy the msix package with the CopyFiles@2 task.
Very well structured and informative video series. Many thanks for all the effort.
Thank you for taking the time to write this! So happy to see the amazing feedback on the series!
Hi, nice video. I also had tried ADO for my MAUI pipelines, but instead of the bash task, I simply use the DotNetCoreCLI task to install the workloads and build the different files for Android, iOS, ...
can you give some example vedio
That makes sense! Thanks for the tip!
Do you know how can we build a .msix file ?
I see the .msix file does get created during the build, but unforutnately the --output parameter does not copy it to our output folder. I'd suggest performing the build locally to see the file structure of the output. You'll find the msix file in a directory similar to: MauiPipelinesDemo\MauiPipelinesDemo\bin\Release
et8.0-windows10.0.19041.0\win10-x64\AppPackages\MauiPipelinesDemo_1.0.0.1_Test\MauiPipelinesDemo_1.0.0.1_x64.msix.
You should be able to copy the msix package with the CopyFiles@2 task.