microsoft / microsoft/WinUI-Gallery
[QA] Improve the csproj & remove the wapproj
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.6k
- Forks
- 756
- Avg merge
- 17h 51m
- Merged PRs (30d)
- 14
Description
WinUIGallery.csproj
The csproj looks really messy primarily due to unnecessary definition of files. For example, we should use wildcards for the content in the Assets folder and the ones for txt files.
WinUIGallery.DesktopWap.Package.wapproj
It doesn't look like used anymore (the CI uses the single project MSIX). The same applies to WinUIGallery.DesktopWap.slnx.
We should WAP related project properties as well (<SingleProject />)
Contributor guide
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
Start by reviewing WinUIGallery.csproj and the existing WinUIGallery.DesktopWap.Package.wapproj and WinUIGallery.DesktopWap.slnx files, then compare them with the CI configuration that builds the single-project MSIX. Clean up unnecessary file definitions, remove the unused WAP project and solution, and update the relevant WAP properties with SingleProject; done means the project remains buildable through the existing CI path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100