Open davidkeaveny opened 2 weeks ago
@davidkeaveny This issue might be a better one to take to the upstream microsoft/component-detection repository? I'm not sure why it's failing to detect your .NET projects, but they should be able to say more. cc: @jamiemagee
I have a repository that contains a mix of ReactJS and .NET Core applications (which use central package management, with a
Directory.Packages.props
file in the root folder). When I run the v0.0.2 tool against the repo, it reports on the NPM packages referenced frompackage.json
, but doesn't report on any .NET packages.My GitHub workflow is:
It will then produce an output like this:
I've tried setting
filePath
to a folder which contains only a .NET project, but it makes no difference, the project isn't scanned and no NuGet packages are reported.