-
Notifications
You must be signed in to change notification settings - Fork 709
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
Broken when referencing a Nuget package in F# interactive #452
Comments
The Let me know if this resolves the issue. |
That project file named in the error message isn't my project file - a new random project file is created each time you run The authentication plugin is broken under F# interactive mode - at least for me. |
Can you give more details on where you are running dotnet fsi? Visual Studio and version? I am able to authenticate and install from an Azure Artifacts feed with dotnet fsi and the cred provider (using the |
I'm on macOS. Using the dotnet sdk installed directly from https://dotnet.microsoft.com/en-us/download I had sdk 7.0.306, I updated to latest sdk 7.0.401 and it is still not working correctly, still getting same message. |
I'm running |
@omcnoe I was able to repro the issue on a MacOS and spoke with a dev on the f# side. TL;DR this is an issue on the f# side not supporting interactive mode when it calls nuget (msbuild) under the hood. I have created a feature request on their repo. On my machine running |
I believe I have the most recent version, but I'm not sure. Is the update process just "run the install again"? |
Yes, we have an install script for macs to make it easy here. Let me know if this does not resolve the issue. |
@omcnoe Any success with the latest version? |
@phil-hodgson no, same exact behavior as before I think the mention of "interactive mode" in the error message is just a red herring. Shouldn't |
I don't use F# but if this uses the same underlying msbuild logic then you should be anle to pass in |
Hi John, sadly Please see the above comment about NuGet "interactive mode" in the error message being a red herring. The problem is that when used by fsi the credential provider is not picking up my existing authentication. |
Is this related? dotnet/fsharp#10609 |
This issue has had no activity in 90 days. Please comment if it is not actually stale. |
Yes issue is still present. |
This issue has had no activity in 90 days. Please comment if it is not actually stale. |
This issue still exists. |
This issue has had no activity in 90 days. Please comment if it is not actually stale. |
Still present |
This issue has had no activity in 90 days. Please comment if it is not actually stale. |
Yes issue is still present. |
In my global Nuget config I have a source that requires authentication.
I've authenticated for this source before.
dotnet restore
works fine and can access packages from this source.But in F# interactive (fsx script or console) all Nuget package commands like
#r "nuget: Microsoft.ABC
fail (even for packages that aren't from the problematic source).Error message:
/Users/omcnoe/stdin(1,1): error FS3217: /usr/local/share/dotnet/sdk/7.0.306/NuGet.targets(156,5): warning : The plugin credential provider could not acquire credentials. Authentication may require manual action. Consider re-running the command with --interactive for 'dotnet', /p:NuGetInteractive="true" for MSBuild or removing the -NonInteractive switch for 'NuGet' [/Users/omcnoe/.packagemanagement/nuget/Projects/--SNIP--/Project.fsproj]
Unlike the error message suggests,
dotnet fsi --interactive
ordotnet --interactive fsi
are not valid commandsThe text was updated successfully, but these errors were encountered: