NuKeeper hangs on NuGet restore command

[CrispyDrone]

I just started playing with NuKeeper again today since I noticed some new activity on the project.

I upgraded to the new version, and tried to rerun the same commands I did after correcting for some now non-existent parameters etc.

I'm currently stuck with the following issues:

1. my .nuget/NuGet.Config file isn't getting picked up any more by NuKeeper (see NuGet.config not found #907)
2. I'm either receiving Unable to load the service index for source or 401 unauthorized for packages of my private nuget feed (see Error on Private Source (AzureDevOps) #542).
3. the nuget restore command hangs indefinitely

Point 1 I can solve by changing %APPDATA%\NuGet\NuGet.Config to include our private nuget feed or passing in the feeds manually using --source.

Point 2 I have exhausted all options. I've experimented with http_proxy settings and packageSourceCredentials using all possible combinations of my PAT (with all scopes enabled), plaintext password, my username, my domainname,... nothing works.

I'm not running behind a proxy as far as I know, I'm connected to my corporate network through a VPN however.

We recently upgraded to Azure Devops Server 2019 from an older TFS2017, and just this morning I had some issues with cloning repositories that was solved by not using the https version of the url see microsoft/Git-Credential-Manager-for-Windows#904

When I run the nuget restore command—that NuKeeper tries to invoke—manually, and remove the -NonInteractive flag, it will prompt me for a username and password, and subsequently successfully restore all packages.

Originally posted by @CrispyDrone in #542 (comment)

[CrispyDrone]

I retried it today using visual studio's devenv command line and it seems to work! See #916. In this case however I was actually using windows cmd and not bash that's included with a git installation on windows.

There are still errors related to Cannot determine the packages folder to restore NuGet packages. Please specify either -PackagesDirectory or -SolutionDirectory.. I don't know the significance of this however since pull requests are being created.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[CrispyDrone]

Bump.

[CrispyDrone]

Fixed by #1044