dotnet-version-detection

Detect .NET TFMs and SDK versions from project files.

10|Updated Jan 28, 2026

Search Tags:#sdk #c##.net #msbuild #tfm #version detection

Ready to run

npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-version-detection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-version-detection
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-version-detection
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-version-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically determines the .NET Target Framework Moniker (TFM) and SDK version used by your project, ensuring compatibility and guiding subsequent development steps.

Core Features & Use Cases

TFM Detection: Identifies the primary .NET TFM from .csproj, Directory.Build.props, or global.json.
SDK Versioning: Extracts the installed .NET SDK version for build context.
Use Case: Before starting any .NET development, run this Skill to confirm your project targets .NET 10 LTS and uses SDK 10.0.100, allowing you to tailor your code to the correct framework features.

Quick Start

Run the dotnet-version-detection skill to analyze the current project's .NET version.

Frequently Asked Questions about dotnet-version-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect the .NET TFM and SDK version used by my project?▼

To detect the .NET TFM and SDK version, analyze your .csproj, global.json, and Directory.Build.props files. This process identifies the primary Target Framework Moniker and extracts the installed SDK version to provide accurate build context and version-specific development guidance.

Why does my .NET project show an incorrect target framework version?▼

An incorrect .NET target framework version often results from MSBuild property indirection or inconsistent file configurations across Directory.Build.props and .csproj files. Resolving these conflicts requires parsing the property hierarchy to identify the effective TFM override.

Can I identify the C# language version from .csproj and Directory.Build.props?▼

Yes, you can identify the C# language version from .csproj and Directory.Build.props by parsing the project files. This detection also identifies preview feature flags, allowing you to tailor code to the specific framework features available.

How do I find the installed .NET SDK version for build context?▼

Find the installed .NET SDK version for build context by examining global.json and project files. This extraction confirms the exact SDK version, such as 10.0.100, ensuring your development environment aligns with the expected build dependencies.

Does MSBuild property indirection affect TFM detection in .NET?▼

MSBuild property indirection directly affects TFM detection in .NET by creating inconsistent file configurations. Accurately resolving these chained properties across Directory.Build.props and .csproj files is required to determine the actual target framework.

When do I need to check the .NET TFM before starting development?▼

You need to check the .NET TFM before starting development to ensure compatibility and guide subsequent steps. Confirming your project targets the correct framework, such as .NET 10 LTS, allows you to tailor your code to the correct framework features.