Add .NET detection with console app and framework detection#2
Closed
dariuszparys wants to merge 1 commit intomicrosoft:mainfrom
Closed
Add .NET detection with console app and framework detection#2dariuszparys wants to merge 1 commit intomicrosoft:mainfrom
dariuszparys wants to merge 1 commit intomicrosoft:mainfrom
Conversation
|
Sure buddy that I will do first thing when I resume working on this after few days |
digitarald
pushed a commit
that referenced
this pull request
Mar 15, 2026
… signals - Add F# language detection via .fsproj files - Add .NET framework detection by parsing project file contents (ASP.NET Core, Blazor, Entity Framework, MAUI, Xamarin, WPF, WinForms, xUnit, NUnit, MSTest, Console) - Expand .NET signal detection to include global.json and Directory.Build.props - Add packages.lock.json to PACKAGE_MANAGERS for NuGet lock file detection - Update instructions prompt to include .fsproj and global.json - Add 7 new tests covering all new detection paths Cherry-picked and improved from #2.
Collaborator
|
Pulled into #60 |
digitarald
added a commit
that referenced
this pull request
Mar 15, 2026
… signals (#60) - Add F# language detection via .fsproj files - Add .NET framework detection by parsing project file contents (ASP.NET Core, Blazor, Entity Framework, MAUI, Xamarin, WPF, WinForms, xUnit, NUnit, MSTest, Console) - Expand .NET signal detection to include global.json and Directory.Build.props - Add packages.lock.json to PACKAGE_MANAGERS for NuGet lock file detection - Update instructions prompt to include .fsproj and global.json - Add 7 new tests covering all new detection paths Cherry-picked and improved from #2. Co-authored-by: Harald Kirschner <digitarald@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request enhances the repository analysis service to better detect .NET projects and their frameworks. It adds deep scanning for .NET project files (
.csproj,.fsproj,.sln), recognizes NuGet as a package manager, and parses project files to identify specific .NET frameworks (like ASP.NET Core, Blazor, MAUI, etc.). Additionally, the tech stack identification instructions are updated to include .NET-related files..NET and NuGet support:
.NETproject signals (e.g.,.csproj,.fsproj,.sln,global.json,packages.lock.json) throughout the repository, not just in the root. This enables more accurate language and framework identification for C# and F# projects. [1] [2]packages.lock.jsonas a NuGet package manager indicator and updated package manager detection logic to recognize NuGet for .NET projects. [1] [2].NET framework detection:
Tech stack identification improvements:
.csproj,.fsproj,.sln,global.json) when identifying the tech stack.