Is your feature request related to a problem? Please describe.
jf audit discovers .NET projects by parsing the solution file, but it only understands the classic .sln; with the new XML-based .slnx it finds no projects and silently scans nothing.
Describe the solution you'd like to see
Make jf audit parse .slnx the same as .sln — enumerate the referenced projects from its XML and build the dependency graph per project - treating both formats as equivalent inputs.
Describe alternatives you've considered
Keeping a parallel .sln, generating a temporary .sln in CI, or running jf audit per .csproj - all are workarounds that add maintenance/CI overhead and are easy to forget.
Is your feature request related to a problem? Please describe.
jf audit discovers .NET projects by parsing the solution file, but it only understands the classic .sln; with the new XML-based .slnx it finds no projects and silently scans nothing.
Describe the solution you'd like to see
Make jf audit parse .slnx the same as .sln — enumerate the referenced projects from its XML and build the dependency graph per project - treating both formats as equivalent inputs.
Describe alternatives you've considered
Keeping a parallel .sln, generating a temporary .sln in CI, or running jf audit per .csproj - all are workarounds that add maintenance/CI overhead and are easy to forget.