You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried adding the Microsoft.Sbom.Targets 2.2.8 package to a project (thus not using the upcoming feature dotnet/sdk#43151) and setting some properties. With .NET SDK 8.0.304, dotnet build and dotnet pack work OK, and the resulting NuGet package contains an SBOM file (although it doesn't contain all the information I expected). However, packing in Visual Studio 2022 does not work:
[REDACTED]\.nuget\packages\microsoft.sbom.targets\2.2.8\buildMultiTargeting\Microsoft.Sbom.Targets.targets(57,5): error MSB6004: The specified task executable location "[REDACTED]\.nuget\packages\microsoft.sbom.targets\2.2.8\buildMultiTargeting\..\tasks\net472\sbom-tool\Microsoft.Sbom.Tool.exe" is invalid.
So it's apparently trying to execute the SBOM CLI Tool as described in #674 (comment):
SbomCLIToolTask.cs is invoked if the MSBuild version targets the "Full" (.NET Framework) runtime bundled with Visual Studio. Because the SBOM API does not support .NET Framework, this class utilizes the SBOM CLI Tool to generate an SBOM.
This is the other blocker for incusion in the .NET SDK IMO - we must be able to support Visual Studio. I believe this is just a packaging issue - the runtime publish outputs from the tool aren't in the package. With a bit of binlog investigation this should be doable.
I tried adding the Microsoft.Sbom.Targets 2.2.8 package to a project (thus not using the upcoming feature dotnet/sdk#43151) and setting some properties. With .NET SDK 8.0.304,
dotnet build
anddotnet pack
work OK, and the resulting NuGet package contains an SBOM file (although it doesn't contain all the information I expected). However, packing in Visual Studio 2022 does not work:So it's apparently trying to execute the SBOM CLI Tool as described in #674 (comment):
but the tool is not included in the package.
Originally posted by @KalleOlaviNiemitalo in #693 (comment)
The text was updated successfully, but these errors were encountered: