Michael Tsfoni
Michael Tsfoni
@Falco20019: The issue I’m running into is that the test `ProjectAssetsFileServiceTests.GetDotnetDependencys_MissingResolvedPackageVersion` mocks a `project.assets.json` file where dependencies under `targets/library/dependencies` have a version range. But I haven’t been able to reproduce...
So I managed to get the error with this constellation. I assume this is basically your problem? ``` net9.0 --- net9.0 all --- > dotnet-cyclonedx .\ProjectA\ProjectA.csproj 1.697s Found the following...
Well, the `-rs` flag is meant for projects that use packages.config instead of `PackageReferences` because those don't create an assets-file. I actually had the idea of adding a warning when...
> I can also open separate issues for each of those if you like to have a better picture and discuss what's the expected behavior first. I will go over...
Seems there was a weird bug in the pipeline, I think I fixed it. Could you rebase your PR?
No, this is alright. The only thing you missed is how strained personal resources in open source projects are. I merge it now.
The core issue is, that a c#-solution is not one software-solution (as in tool, library or service) but rather an arbitrary collection of one or more software-solution or parts of...
I am unable to reproduce the underlying problem. Could you describe, how I need to setup a solution to run into the error?
Should work till version 2.10 I will have a look soon, shouldn't be a big issue to fix
Merged it. Released in 4.1.0