Drop MSIX scaffold cruft so VS stops demanding deployment

[StuartMeeks]

Problem

F5 in Visual Studio failed with:

The project needs to be deployed before we can debug. Please enable Deploy in the Configuration Manager.

Deploy was already checked. The advice is for MSIX-packaged projects; unpackaged WinUI 3 apps shouldn't have Deploy checked at all, AND shouldn't have the MSIX tooling enabled in the csproj.

Root cause

The csproj still carried <EnableMsixTooling>true</EnableMsixTooling> + the conditional Msix ProjectCapability / HasPackageAndPublishMenu blocks from the template, which made VS classify the project as needing MSIX deployment. WindowsPackageType=None says we ship unpackaged, so the deploy step finds nothing to deploy and the F5 path errors out.

CLAUDE.md is explicit:

Unpackaged distribution. This is load-bearing — do not reintroduce MSIX / packaged assumptions.

Changes

• Remove EnableMsixTooling, the conditional Msix ProjectCapability, and the HasPackageAndPublishMenu block from Snipdeck.App.csproj
• Remove <Deploy /> from Snipdeck.App in the slnx so the build doesn't try to run a deploy step
• Delete Package.appxmanifest (only meaningful for MSIX-packaged builds)
• Delete Assets/*.png (the Start tile / store / lock screen images those manifests pointed at) and the Content Include entries that referenced them
• The Win32 app.manifest stays (DPI awareness, etc.) and is unrelated

Test plan

• dotnet test tests/Snipdeck.Core.Tests — still green
• You: F5 in Visual Studio no longer demands deploy and the window comes up
• CI's Windows job still builds the App project (any reference to a deleted asset would surface here)

🤖 Generated with Claude Code