dotnet-solution-navigation

To find a .NET application entry point, locate traditional Program.cs files, top-level statements, or worker service configurations. The skill provides discovery commands and heuristics to pinpoint where execution starts across various project types quickly.

Parsing .sln and .slnx files lists all included projects and their structural relationships. The skill traverses these solution files to map out project dependencies and identify how different components connect within the codebase.

Mapping project dependencies in a .NET solution involves traversing the project dependency graph. This identifies code relationships and clarifies the impact of changes, reducing time spent manually tracing references during codebase exploration.

Locating configuration files like appsettings.json and launchSettings.json is done using specific discovery heuristics. The skill scans the solution layout to identify these critical files for understanding application configuration and launch profiles.

Yes, the navigation approach works with .NET test projects and worker services. It covers traditional Program.cs, top-level statements, and worker service layouts, offering discovery commands tailored to these specific project types.

Traversing a project dependency graph is needed when onboarding to a new .NET project or assessing the impact of code changes. It maps code relationships to provide a rapid overview of the solution's architecture.