-
Notifications
You must be signed in to change notification settings - Fork 809
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
fsi bug after .NET 9 update: non-HTTPS sources in nuget.config creates error even with allowInsecureConnections="true" config #18424
Comments
Thanks for the report. |
I am especially after if FSI is doing anything unusual or if a plain (non-FSI, even non F#) would be doing the same. |
There are other projects, csproj and fsproj projects. They don't generate any error with this update. Nuget packages are installed without an issue. Only dotnet fsi commands are effected. |
Here is the generated file @T-Gro
By the way, it sometimes does not generate that error, but if you reference a package from that http source, it will generate error |
fsi bug after .NET 9 update: non-HTTPS sources in nuget.config creates error even with allowInsecureConnections="true" config
Repro steps
Provide the steps required to reproduce the problem:
As you see, we have an http source, and allowInsecureConnections config to disable error.
dotnet fsi
#r "nuget: Newtonsoft.Json, 13.0.3";;
and hit enterExpected behavior
This should work like in the older .net version. Import the package. The package isnt even in that non-https source.
Actual behavior
I am unable to have a non-https nuget source in my nuget.config file. Imports create error
Known workarounds
Removing that non-https source from nuget.config while using fsi scripts
Related information
The text was updated successfully, but these errors were encountered: