APPX0702 when csproj reference vcxproj which output only winmd
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 665
- Forks
- 134
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
Description
When reference a pure winmd vcxproj project to a package csproj such as UWP or WAS, it always including the not exist .dll file, which cause the APPX0702 error.
Steps To Reproduce
- Create a pure
winmdvcxprojsuch as https://github.com/SharpAdb/AdvancedSharpAdbClient.SampleApp/blob/main/SharpADB/SharpADB.Metadata/SharpADB.Metadata.vcxproj - Reference it
Expected Behavior
Works fine.
Version Info
- Microsoft.Windows.CsWinRT
2.2.0 - Microsoft.Windows.SDK.BuildTools
10.0.26100.4654 - Microsoft.Windows.SDK.BuildTools.MSIX
1.7.20250806.1
Additional Context
I don't know which project is for Microsoft.Windows.SDK.BuildTools, but this is a csproj problem so I write the issue here. If this issue is in wrong place, please move it to the right one.
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 with the referenced SharpADB.Metadata.vcxproj and reproduce the reference from a UWP or WAS csproj using the listed CsWinRT and SDK BuildTools versions. Trace the generated package inputs around APPX0702; done means a winmd-only vcxproj reference no longer adds a nonexistent .dll.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, csharp
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100