microsoft / microsoft/msix-packaging
MSIX build AzDO task should fail if it doesn't build an msix package
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
The build task just calls MSBuild with the appropriate parameters to create a package, assuming that the solution already has a Windows Application Packaging project. If the solution has that project, then everything works fine and the package is created. But if it doesn't or if it is not configured properly, then there is nothing that uses the properties in the command line and the package is not created.
This is not being treated as an error, since MSBuild simply succeeds without knowing that it didn't do what we wanted it to do. We should detect that a package was created and fail if it wasn't.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the MSIX build AzDO task and inspect how it determines the package output after invoking MSBuild. Run it against a solution without a Windows Application Packaging project or with incorrect configuration; done means the task fails when no MSIX package is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100