Menu
Avoid `.App` executable assembly names for runnable .NET samples on macOS
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive package defaults, release packaging, and website version display from one MSBuild property
Validate every meaningful workflow_dispatch input combination before approving release-pipeline changes
Keep mixed validation/release GitHub workflow dispatch inputs from misrouting validation runs
Validate NuGet release artifacts before publish and ensure both package and symbol payloads are release-correct
Ship an Astro docs site to GitHub Pages with SEO, validation, and custom-domain safety checks
Keep repo-local .NET sample apps zero-config by avoiding native apphosts when macOS integrity enforcement can kill them
| name | macos-apphost-naming |
| description | Avoid `.App` executable assembly names for runnable .NET samples on macOS |
| domain | dotnet-samples |
| confidence | medium |
| source | earned while fixing Sample.Simplified startup |
macOS treats .app names specially. For runnable .NET projects, an executable assembly name that ends with .App can make dotnet run fail even though the underlying program and tests are otherwise healthy.
.App for console apps and samples that developers launch with dotnet rundotnet run --no-build and asserts a zero exit code plus a recognizable success stringsamples/Sample.Simplified/Sample.Simplified.App/Sample.Simplified.App.csproj
RootNamespace as Sample.Simplified.AppAssemblyName to Sample.Simplified.Demosamples/Sample.Simplified/Sample.Simplified.Tests/EndToEnd/StartupSmokeTests.csSomething.App and relying only on in-process unit tests; that misses the launch failure path that dotnet run exercises on macOS