Comments (6)
I had followed Manual installation on Linux and Mac to the default location of $HOME/.nuget/plugins
.
I hadn't set $NUGET_PLUGIN_PATHS
but I have since set that to $HOME/.nuget/plugins
. Now when I run nuget restore or dotnet restore it says "A plugin was not found at path '/home/myUsername/.nuget/plugins'."
I verified /home/myUsername/.nuget/plugins/netcore/CredentialProvider.Microsoft/CredentialProvider.Microsoft.dll
does exist.
from artifacts-credprovider.
Can you share the details of the command that you're trying to run? If you're running the dotnet
command for example, the first time you might have to run it with the --interactive
switch.
from artifacts-credprovider.
Should also mention I'm trying to run this in WSL using Ubuntu 18.04
I was running nuget restore
with nuget version 5.2.0.6090. The username/password prompt I get is right in the command prompt rather than launching a new window of any kind.
I tried dotnet restore --interactive
but that never even prompts me and just fails with some more general errors about Unable to load the service index for source
.
I was wondering if maybe I installed the plugin on my normal nuget install and maybe the dotnet install has it's own bundled nuget that it uses which may be a bit older? I'm not sure what nuget install is actually used by the dotnet cli though.
from artifacts-credprovider.
If you get the username and password prompts in the console, it likely means that NuGet wasn't able to find the plugin. Did you run one of these scripts to install the cred provider? Please refer to the readme for instructions how the plugin will be discovered. For nuget you need to install the netfx version and for dotnet you will need the netcore version.
from artifacts-credprovider.
It looks like you've tried with both nuget and dotnet. Dotnet uses the netcore version and nuget uses the netfx version of the plugin, so both need to be installed in $HOME\.nuget\plugins
if you want both to work.
You must set the $NUGET_PLUGIN_PATHS environment variable to the CredentialProvider.Microsoft.dll (or CredentialProvider.Microsoft.exe with nuget) instead of the folder. If you have to use both nuget and dotnet, I believe with nuget 5.3 update there are two separate environment variables that you can set, one for the .dll and one for the .exe files: NuGet/Home#8151
Although, if you have the CredentialProvider.Microsoft.dll in $HOME\.nuget\plugins\netcore\CredentialProvider.Microsoft
, and CredentialProvider.Microsoft.exe in $HOME\.nuget\plugins\netfx\CredentialProvider.Microsoft
, both dotnet and nuget should be able to find the plugin as long as an appropriate version of the tool is used.
from artifacts-credprovider.
Closing the issue due to inactivity. Please refer to the previous comment on how to make nuget/dotnet discover the cred provider plugin. Let me know if you have any questions.
from artifacts-credprovider.
Related Issues (20)
- Azure Artifacts Credential provider failing to start HOT 6
- NullReferenceException in v1.0.9 HOT 3
- Azure Devops: gzip: stdin: unexpected end of file HOT 3
- Problem starting the plugin - Broken Pipe HOT 1
- How to do enhanced debugging? HOT 1
- Issue authenticating to Azure Artifacts via Python behind firewall decryption HOT 1
- Use Windows authentication context from in WSL HOT 6
- System.Security.Cryptography.CryptographicException on remote connections HOT 9
- The last Create 1.1.0 release Build Failed. When v1.1.0 will be released? HOT 6
- The messages logged by the credential providers are not localized. HOT 3
- Inconsistent account selection modal behavior across operating systems HOT 3
- MsalInteractiveTokenProvider breaks if no console window handle available HOT 4
- Artifacts Conda Remove SDK Dependency HOT 2
- Credential provider is not working on new laptop HOT 4
- `JsonException` with Release `1.1.0` when using `VSS_NUGET_EXTERNAL_FEED_ENDPOINTS` HOT 4
- dotnet list <SOLUTION> package --vulnerable/--outdated/--deprecated fails with Azure Artifacts Credential Provider HOT 7
- Are the Requirements Correct? HOT 4
- The proxy tunnel request to proxy failed with status code '407' HOT 1
- .NET 8 is not supported yet
- nuget not prompting for credentials when querying Azure Artifacts feed on WSL HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from artifacts-credprovider.