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
/usr/local/share/dotnet/sdk/6.0.419/Sdks/NuGet.Build.Tasks.Pack/buildCrossTargeting/NuGet.Build.Tasks.Pack.targets(221,5): error NU5026: The file '/Users/pavankumarhu/scripts/wopivalidator/wopi-validator-core/src/WopiValidator/bin/Release/net6.0/Microsoft.Office.WopiValidator.dll' to be packed was not found on disk. [/Users/pavankumarhu/scripts/wopivalidator/wopi-validator-core/src/WopiValidator/WopiValidator.csproj]
The text was updated successfully, but these errors were encountered:
pkumaroapps
changed the title
nsall WOIP VALIDATOR on MAC M2 (osx-arm64)
WOIP VALIDATOR on MAC M2 (osx-arm64)
Mar 14, 2024
Hello!
I am trying to insall WOIP VALIDATOR on MAC M2 (osx-arm64).
I Built a self-contained package with the command :
dotnet publish -c Release -f net6.0 -r osx-arm64
I built Basic unit tests running the dotnet test command:
dotnet test ./test/WopiValidator.Core.Tests/WopiValidator.Core.Tests.csproj -c Release
But when I try to Pack the NuGet package. with command, I am encountering an issue.
dotnet pack -c Release
can you please assist me in resolving this particular issue?
MSBuild version 17.3.2+561848881 for .NET
Determining projects to restore...
All projects are up-to-date for restore.
WopiValidator.Core -> /Users/pavankumarhu/scripts/wopivalidator/wopi-validator-core/src/WopiValidator.Core/bin/Release/net6.0/Microsoft.Office.WopiValidator.Core.dll
/usr/local/share/dotnet/sdk/6.0.419/Sdks/NuGet.Build.Tasks.Pack/buildCrossTargeting/NuGet.Build.Tasks.Pack.targets(221,5): error NU5026: The file '/Users/pavankumarhu/scripts/wopivalidator/wopi-validator-core/src/WopiValidator/bin/Release/net6.0/Microsoft.Office.WopiValidator.dll' to be packed was not found on disk. [/Users/pavankumarhu/scripts/wopivalidator/wopi-validator-core/src/WopiValidator/WopiValidator.csproj]
The text was updated successfully, but these errors were encountered: