Repository navigation
bug: detectProjectType() misses .slnx (modern Visual Studio solution format) #124
Description
Problem
detectProjectType() in index.js detects .NET projects by checking for .csproj and .sln files, but does not check for .slnx — the modern Visual Studio solution format introduced in VS 2022 17.x.
Repos using .slnx (like bradygaster/SqncR) are classified as unknown and receive generic stub workflows with TODO comments instead of .NET-appropriate workflow hints.
Reproduction
SqncR has SqncR.slnx + Directory.Build.props but no .csproj at the root. Running upgrade on this repo produces generic workflow stubs.
Expected
detectProjectType() should return 'dotnet' for repos containing any of:
*.csproj*.sln*.slnx← missing*.fsproj← also missing*.vbproj← also missing
Fix
Add *.slnx, *.fsproj, *.vbproj to the .NET detection glob in detectProjectType().
Found by: Hockney during 0.5.0 diagnostic investigation on SqncR.
Activity
chore: log 0.5.0 investigation session — bugs #124 #125 #126
fix: upgrade --migrate-directory now completes full upgrade (v0.5.2)
fix: upgrade --migrate-directory now completes full upgrade (v0.5.2)
fix: upgrade --migrate-directory now completes full upgrade (v0.5.2)
bradygaster commentedon Feb 20, 2026
Fixed in v0.5.2. Added *.slnx, *.fsproj, and *.vbproj\ to \detectProjectType()\ in \index.js. Validated against bradygaster/SqncR (\SqncR.slnx).
[dgrep-cli] Phase 1.2: Config file management (github#102) (github#124)