4

I'm having problem restoring packages for a dotnet core 2.0 project here in Bolivia. Back home in The Netherlands I have no problems restoring the packages, but here it breaks.

I'm getting a lot of errors like:

Failed to download package 'System.Linq.4.1.0' from
'https://api.nuget.org/v3-flatcontainer/system.linq/4.1.0/system.linq.4.1.0.nupkg'.
An error occurred while sending the request
  Error: SecureChannelFailure (Unable to write data to the transport connection: Cannot access a disposed object.
  Object name: 'System.Net.Sockets.Socket'..)
  Unable to write data to the transport connection: Cannot access a disposed object.
  Object name: 'System.Net.Sockets.Socket'..
  Cannot access a disposed object.
  Object name: 'System.Net.Sockets.Socket'.
Unable to load package 'System.Linq'.

When I try to wget this file I'm getting between 400 KB/s and 3 MB/s.

I'm thinking it's nuget restoring the packages in parallel and that causes the Hostel internet to be fully used? I have tried it in different Hostels/Cafe's here, and I'm getting the same problems. When I Remote Desktop into my home server in the Netherlands and restore the packages for the same project it's all going well.

What are my options here? I tried googling this problem for a while, but I haven't found a solution yet.

Thanks!

Jorik

Lex Li
  • 60,503
  • 9
  • 116
  • 147
Jorik
  • 239
  • 1
  • 4
  • 14

4 Answers4

7

I cannot help with the networking problem but you may be able to reduce the amount of NuGet packages that are being downloaded by Visual Studio for Mac as a possible workaround. This can be done for a .NET Core 2.0 project by using the NuGet fallback folder:

/usr/local/share/dotnet/sdk/NuGetFallbackFolder/

The fallback folder holds many NuGet packages that are used by .NET Core 2.0 by default. This folder should be created if you install the .NET Core SDK.

Using the above folder will prevent a lot of NuGet packages from being downloaded.

You can either add it directly as a NuGet package source or edit your ~/.config/NuGet/NuGet.Config file and add the fallback folder as follows:

Alternatively you could add an explicit fallback folder into your ~/.config/NuGet/NuGet.Config file:

<fallbackPackageFolders>
  <add key="DotNetCore2FallbackFolder" value="/usr/local/share/dotnet/sdk/NuGetFallbackFolder" />
</fallbackPackageFolders>

Visual Studio for Mac would need to be restarted. Also check that the folder exists.

Note that due to another bug Visual Studio for Mac will still download a few NuGet packages when restoring a .NET Core project.

Matt Ward
  • 47,057
  • 5
  • 93
  • 94
  • Can you not use the local package cache as a source for .NetCore projects? i.e. `~/.nuget/packages` (Which works fine for non-NetCore projects) – SushiHangover Sep 09 '17 at 18:42
  • The local package cache is used for .NET Core projects. However if the NuGet packages were available in the cache then NuGet would not need to go online - which seems to be the cause of the problem. – Matt Ward Sep 09 '17 at 19:03
  • Thanks... I'll have to double check the latest VS4M as I have always had to disable the default repo (`nuget.org`) and enable the local file source I added (~/.nuget/packages) to prevent the online check and eventual timeout error (I have a *really* high latency net connection that causes great pains for VS4M during restores (crashes, infinite hangs, unable to "abort" the restore, etc...) – SushiHangover Sep 09 '17 at 19:12
  • Hi Matt, can you vote the synonyms part? https://stackoverflow.com/tags/visual-studio-mac/synonyms – Lex Li Nov 13 '17 at 23:36
2

What are my options here? I tried googling this problem for a while, but I haven't found a solution yet.

Obviously, the reason for this error is the networking problem, however, just as Matt said, we could not give you much much help for the networking problem. I would like provide another workaround:

Since nuget restore the packages from local package cache by default and you can restore packages successfully in your home server in the Netherlands:

You can copy those packages from you home server and add them into local package cache C:\Users\username\.nuget\packagesto your machine in Bolivia.

Hope this helps.

Leo Liu
  • 71,098
  • 10
  • 114
  • 135
1

You could also try to disable restoring multiple packages in parallel with the Nuget argument -DisableParallelProcessing.

see here: https://learn.microsoft.com/en-us/nuget/tools/cli-ref-restore

Pepper
  • 194
  • 11
0

This is most likely a Mono runtime bug, reported here: https://github.com/mono/mono/issues/19893

The workaround is indeed to disable parallel restore by passing /p:RestoreDisableParallel=true property to MSBuild.

Kirill Osenkov
  • 8,786
  • 2
  • 33
  • 37