Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/dotnet upgrade #35

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

milbrandt
Copy link

Description

Builds are failing on Azure DevOps server after cleanup build server of work directory.
Used task: matthid.paket-credential-manager.set-paket-credential-manager.setCredentialManager@0

Possible Performance degradation, blacklist '2_https://nuget.org/api/v2/Packages?$filter=(tolower(Id) eq 'fsharp.control.reactive') and (Version eq '4.5.0')'
Source 'https://api.nuget.org/v3/index.json' exception: System.Exception: Could not retrieve data from 'https://nuget.org/api/v2/FindPackagesById()?semVerLevel=2.0.0&id='FSharp.Control.Reactive''
---> Paket.CredentialProviderUnknownStatusException: Credential provider returned an invalid result (-2147450730): 
Standard Error: It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '2.0.0' was not found.
  - The following frameworks were found:
     3.1.10 at [D:\_2\_tool\dotnet\shared\Microsoft.NETCore.App]

Proposed changes:

  • create CredentialProvider as self-contained windows .Net 5.0 app
  • update of npm packages
  • use fake as local dotnet tool

TODO

  • Updated tasks have updated versions.
  • Testing

@Flohack74
Copy link

Is there any movement on this? Our pipeline has .NET 2.x only because of paket tasks still inside, and I would love to get rid of it...

@milbrandt
Copy link
Author

Is there any movement on this? Our pipeline has .NET 2.x only because of paket tasks still inside, and I would love to get rid of it...

I assume, @isaacabraham abandoned this repo as the last commit was nearly 4 years ago. Thus from my side there will be no upgrade on the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants