메뉴
Avoid `.App` executable assembly names for runnable .NET samples on macOS
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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
SOC 직업 분류 기준
| 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