Add DotNet Component Adapter #994
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
This update should resolve issue #972 |
DaveTryon
reviewed
Mar 31, 2025
src/Microsoft.Sbom.Adapters/Adapters/ComponentDetection/DotNetComponentExtensions.cs
Show resolved
Hide resolved
Contributor
|
/azp run |
Contributor
|
/azp run |
DaveTryon
approved these changes
Apr 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
New DotNet component contract was added upstream in component detection. The detector is still in experimental phase, but we want to be able to deserialize the contract successfully and generate SBOM when ready.
⚙️ Changes
Some other updates were included in the version upgrade