You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Loading nuget package in FSI fails when a source path contains accentuated character #12401
I don't know if any progress have been made on this issue, but I just noticed it raises when using #r "nuget: whatever" from a Dotnet Interactive C# cell code. So the problem looks wider than F#, probably from the Nuget Package Manager.
Edit: it happens in C# Interactive as well. Where should I bring this issue ? Nuget.Client ? Dotnet Interactive ? Csharplang ?
Edit 2 : pointless remark about C# Interactive stroked, my CSI version doesn't support nuget reference.
@vzarytovskii : in this sentence I meant it happens in CSI, but my bad, CSI doesn't support nuget reference. But as I told in the previous sentence, yes it does happens in C# (and F#) code cells in .NET Interactive.
FSI error message : stdin(1,1): error FS3217: The source directory 'C:\Beyonc%EF%BF%BD' not found
.NET interactive error message (both C# or F# cell code) : Error: PackageManagement Error 3217 Le répertoire source 'C:\Beyonc%EF%BF%BD' est introuvable (same message as FSI except localized)
The dependency manager is an FSI component that is used by dotnet interactive to handle package management. Whenever I talk about #r nuget , the dependency manager is what I am talking about, wherever it is surfaced.
But if the source is unreachable, I get an error error FS3217: The source directory '\\network\repos' not found. IMHO, that would be better as a warning, then produce an error if a package itself is unreachable. That point being outside the scope of the described issue, I'm closing it anyway.
Activity
KevinRansom commentedon Nov 16, 2021
@JDiLenarda ,
Thanks for reporting this, the restore source is not escaped, when included for resolution. We will address this.
Thanks,
Kevin
JDiLenarda commentedon Jul 8, 2022
I don't know if any progress have been made on this issue, but I just noticed it raises when using
#r "nuget: whatever"from a Dotnet Interactive C# cell code. So the problem looks wider than F#, probably from the Nuget Package Manager.Edit:
it happens in C# Interactive as well.Where should I bring this issue ? Nuget.Client ? Dotnet Interactive ? Csharplang ?Edit 2 : pointless remark about C# Interactive stroked, my CSI version doesn't support nuget reference.
vzarytovskii commentedon Jul 8, 2022
You mean in the C# cell in the .NET interactive? In this case, I think it's still the dependency manager.
JDiLenarda commentedon Jul 8, 2022
@vzarytovskii : in this sentence I meant it happens in CSI, but my bad, CSI doesn't support nuget reference. But as I told in the previous sentence, yes it does happens in C# (and F#) code cells in .NET Interactive.
FSI error message :
stdin(1,1): error FS3217: The source directory 'C:\Beyonc%EF%BF%BD' not found.NET interactive error message (both C# or F# cell code) :
Error: PackageManagement Error 3217 Le répertoire source 'C:\Beyonc%EF%BF%BD' est introuvable(same message as FSI except localized)vzarytovskii commentedon Jul 8, 2022
I see, yeah, it sounds like it is handled by dependency manager.
KevinRansom commentedon Nov 17, 2022
The dependency manager is an FSI component that is used by dotnet interactive to handle package management. Whenever I talk about #r nuget , the dependency manager is what I am talking about, wherever it is surfaced.
KevinRansom commentedon Nov 17, 2022
@JDiLenarda --- This seems to be working for me. Can you verify that you still have an issue with this:
Thanks
Kevin
KevinRansom commentedon Nov 17, 2022
Also the disabled sources bug was fixed a few months ago. Thanks
JDiLenarda commentedon Nov 20, 2022
@KevinRansom
It's an improvement on the following points :
But if the source is unreachable, I get an error
error FS3217: The source directory '\\network\repos' not found. IMHO, that would be better as a warning, then produce an error if a package itself is unreachable. That point being outside the scope of the described issue, I'm closing it anyway.