Arcade: Tasks.Feed.dll : Could not load file or assembly 'NuGet.Common, Version=5.3.0.4

Created on 12 Nov 2019  Â·  12Comments  Â·  Source: dotnet/arcade

The following builds failed with the error mentioned in the title:

##[error].packages\microsoft.dotnet.arcade.sdk\5.0.0-beta.19558.11\tools\Publish.proj(162,5): error MSB4062: The "PushToAzureDevOpsArtifacts" task could not be loaded from the assembly F:\workspace\_work\1\s\.packages\microsoft.dotnet.build.tasks.feed\5.0.0-beta.19529.3\build\../tools/netcoreapp2.1/Microsoft.DotNet.Build.Tasks.Feed.dll. Could not load file or assembly 'NuGet.Common, Version=5.3.0.4, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Could not find or load a specific file. (0x80131621) Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

I think we dealt with a similar (same) problems a few days ago... Perhaps all we need is to update the Tasks.Feed lib in the affected repo?

/cc @mmitche @riarenas @MattGal

First Responder

Most helpful comment

@AdamYoblick - just tell the dentist to take a break from drilling for a moment and check stuff in. :)

All 12 comments

It's because the dotnet SDK in use in the repo is tool old. Updating will work.

Pinging repo owners for awareness: @dotnet/dotnet-winforms @dougbu

@AdamYoblick and @RussKie can you guys take care of this ASAP?

I already opened a PR.

@AdamYoblick - just tell the dentist to take a break from drilling for a moment and check stuff in. :)

There are some test failures that need dealing with https://github.com/dotnet/winforms/pull/2357

@mmitche - the CI build is failing for your PR, had you investigated it?

 ##[error]XUnit(0,0): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Tests failed: D:\a\1\s\artifacts\TestResults\Release\System.Windows.Forms.Tests_netcoreapp5.0_x64.html [netcoreapp5.0|x64]

I had not.

Update:

If EF6 build passes (it will take 1h30m to test it) I'll close this issue.

Yes we updated the SDK in EF6 to fix this issue. It should be passing now.

EF6 build passed.

Was this page helpful?
0 / 5 - 0 ratings