Michael Tsfoni

I assume something happens in the GitHub actions environment causing the .pdbs to come out with unexpected paths. I found this [work around,](https://github.com/CycloneDX/cyclonedx-dotnet-library/commit/a27d9238e253681fcfbcfa2a3585f27974eb44e0) which currently is good enough for me.

Should be fixed in 0.25.1

The spdx schema in the library was updated with 0.25.1. Please let me know if there is still an issue.

Changing the csv to a json seems like it doesn't make sense. You can reopen or re-request with an explanation.

I think the cyclonedx.core library support this already. So it's pretty straight forward: Adding a new argument. I suggest -b // --bom-format with an enumeration. Default is XML. --json can...

Hello dreammaster38, unfortunately, you didn't sign-off your commits, thus I cannot merge them. Please consider signing them off. See here for some more information: https://github.com/CycloneDX/cyclonedx-dotnet/pull/748/checks?check_run_id=15953566656

You are right, it doesn't. That also seems a little trickier as the asset file, doesn't give the information directly. Looks like I'd have to check the dependency graph and...

I will certainly solve this, as I consider it a bug. But I need to shift some things around in the process to make it work, so this is bigger...

> @mtsfoni will this fix also result in dependencies of the dev dependency also having their scope classified as excluded as I am needing that fixed as part of this....

#847 and #848 basically has the solution to the problem that we discussed regarding figuring out what is a dev dependency and what not. Unfortunately, the PR is like 90%...