[Spec] Publishing MAUI apps should be consistent across platforms from the command line for CI/CD

[Redth]

Goal: Make dotnet publish relatively consistent and relatively free of platform specific arguments required...

Consider the following scenario for building in CI:
dotnet publish -f net6.0-android -c Release -o ./artifacts

Expected output:

• ./artifacts/com.app.id.aab (Signed)
• ./artifacts/com.app.id.apk (Signed)

dotnet publish -f net6.0-ios -c Release -o ./artifacts

Expected output:

• ./artifacts/com.app.id.app

• ./artifacts/com.app.id.ipa

• Android Make dotnet publish more consistent android#6393

• iOS Make dotnet publish more consistent  xamarin/xamarin-macios#12997

[jonathanpeppers]

I remember there was some talk about making dotnet build be "the way" and potentially deprecating dotnet publish. (I can't find a public GitHub issue on it, though). I know the WASM team was going to move to using dotnet build as much as possible.

Is there a reason dotnet build -c Release isn't sufficient here? It also has an -o argument; that just changes bin\Release\ to something else.

[jfversluis]

Also see:

• .NET MAUI Android target publishing/archiving #4377
• .NET MAUI iOS target publishing/archiving #4397
• .NET MAUI Windows target publishing/archiving #4329
• .NET MAUI macOS target publishing/archiving #5399

[HobDev]

Building CI/CD pipeline would become simpler with this.

[RichardMarsh]

Would just like to add that this would be great. We are using CI/CD to produce the apps and push them to app center. Right now the tooling to do this doesn't feel well documented or consistent for iOS and Android.