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
dotnet list path\to\solution\file.sln package --vulnerable
I receive the error
No assets file was found for <project-file>. Please run restore before running this command.
then running dotnet restore path\to\solution\file.sln
fails with
error MSB4126: The specified solution configuration "Debug|x64" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (
e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration.
Unfortunately, neither dotnet restore nor dotnet list package support --platform or --configuration or forwarding of /p:MSBuildVariable=Value arguments.
The functionality of dotnet restore can be easily replicated by calling msbuild /t:Restore /p:... however, afaik, there is no such workaround for the dotnet list package --vulnerable feature...
Additional Context and Details
The solution/projects in question use alternate platform names such as MyPlatformName instead of x64.
The text was updated successfully, but these errors were encountered:
NuGet Product(s) Involved
dotnet.exe
The Elevator Pitch
when trying to run:
dotnet list path\to\solution\file.sln package --vulnerable
I receive the error
then running
dotnet restore path\to\solution\file.sln
fails with
Unfortunately, neither
dotnet restore
nordotnet list package
support--platform
or--configuration
or forwarding of/p:MSBuildVariable=Value
arguments.The functionality of
dotnet restore
can be easily replicated by callingmsbuild /t:Restore /p:...
however, afaik, there is no such workaround for thedotnet list package --vulnerable
feature...Additional Context and Details
The solution/projects in question use alternate platform names such as
MyPlatformName
instead ofx64
.The text was updated successfully, but these errors were encountered: