Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tool gives an error if folder contains more than one project file #919

Closed
VijayB2606 opened this issue Jan 3, 2025 · 3 comments
Closed
Assignees
Labels
good first issue Good for newcomers help wanted Extra attention is needed ready for development Issue is sufficiently defined and suitable for contributors to start working

Comments

@VijayB2606
Copy link

We are explicitly specifying project file path in the cyclonedx command. But then also tool gives below error if a folder contains multiple project files.

"Specify which project file to use because this contains more than one project file."

Please resolve this issue.

Image

@github-actions github-actions bot added the triage Don't know what to do with this yet label Jan 3, 2025
@mtsfoni
Copy link
Contributor

mtsfoni commented Feb 1, 2025

This is most likely caused by one of the dotnet calls that cyclonedx makes.
We should make sure, it always specifiies the project in those calls.

@mtsfoni mtsfoni added bug Something isn't working help wanted Extra attention is needed good first issue Good for newcomers ready for development Issue is sufficiently defined and suitable for contributors to start working and removed triage Don't know what to do with this yet labels Feb 1, 2025
@mtsfoni mtsfoni self-assigned this Feb 2, 2025
@mtsfoni
Copy link
Contributor

mtsfoni commented Feb 2, 2025

See here
dotnet/sdk#9623

It's a bug in the dotnet sdk.

Try calling `dotnet-CycloneDX .\ConsoleApp1.csproj' instead of 'dotnet cyclonedx .\ConsoleApp1.csproj'.
That worked for me.

I am considering updating all the calls in the readme.md.

@mtsfoni mtsfoni removed the bug Something isn't working label Feb 2, 2025
mtsfoni added a commit that referenced this issue Feb 2, 2025
@mtsfoni
Copy link
Contributor

mtsfoni commented Feb 2, 2025

updated the readme-file.

@mtsfoni mtsfoni closed this as completed Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed ready for development Issue is sufficiently defined and suitable for contributors to start working
Projects
None yet
Development

No branches or pull requests

2 participants