The phylum command treats .csproj files differently when passed as arguments to the command line as opposed to when they are found by a directory search... Specifically, running phylum parse sample.csproj will detect the file as type msbuild, while running phylum parse with no files and letting the tool find it will detect the file as nugetlock.

(The specifics here will change after #1435 is merged, but this problem may extend to other formats, so I wanted to track it separately)

> phylum status
Project: null
Group: null
Project Root: null
Dependency Files:
 - path: ./sample.csproj
   type: nugetlock

> phylum analyze -p foo sample.csproj
✅ Successfully parsed dependency file "sample.csproj" as type "msbuild"