Agent skill · software engineering · aaronontheweb
dotnet-project-structure
Modern .NET project structure including .slnx solution format, Directory.Build.props, central package management, SourceLink, version management with RELEASE_NOTES.md, and SDK pinning with global.json.
Why this skill is useful
Provides detailed guidance on modern .NET project structures and specific commands for migration and configuration that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-07-03. 1,095 stars on the source repository.
What this skill does
.NET Project Structure and Build Configuration When to Use This Skill Use this skill when: Setting up a new .NET solution with modern best practices Configuring centralized build properties across multiple projects Implementing central package version management Setting up SourceLink for debugging and NuGet packages Automating version management with release notes Pinning SDK versions for consistent builds Related Skills dotnet-local-tools - Managing local .NET tools with dotnet-tools.json microsoft-extensions-configuration - Configuration validation patterns --- Solution File Format (.slnx) The .slnx format is the modern XML-based solution file format introduced in .NET 9. It replaces the traditional .sln format. Benefits Over Traditional .sln Aspect .sln (Legacy) .slnx (Modern) -------- --------------- ---------------- Format Custom text format Standard XML Readability GUIDs, cryptic syntax Clean, human-readable Version control Hard to diff/merge Easy to diff/merge Editing IDE required Any text editor Version Requirements Tool Minimum Version ------ ----------------- .NET SDK 9.0.200 Visual Studio 17.13 MSBuild Visual Studio Build Tools 17.13 Note: Starting with .NET 10, dotnet new sln creates .slnx files by default. In .NET 9, you must explicitly migrate or specify the format. Example .slnx File Migrating from .sln to .slnx Use the dotnet sln migrate command to convert existing solutions: Important: Do not keep both .sln and .slnx files in the same repository. This causes issues with automatic solution detection and can lead to sync problems. After migration, delete the old .sln file. You can also migrate in Visual Studio: 1. Open the solution 2. Select the Solution in Solution Explorer 3. Go to File > Save Solution As... 4. Change "Save as type" to Xml Solution File (.slnx) Creating a New .slnx Solution Recommendation If you're using .NET 9.0.200 or later, migrate your solutions to .slnx. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aaronontheweb/project-structure