Repro steps
-
Ctrl + N in Visual Studio and select F# script
-
Add #r "nuget: ini-parser" to the file
It's important to type this into the file instead of pasting from the clipboard.
-
Observe C:\Users\...\.nuget\packages
Expected behavior
Only ini-parser directory should appear.
Actual behavior
The following directories appear:
in/1.0.0/
ini/1.0.7/
ini-parser/3.4.0/
Every package on nuget.org whose ID is a prefix of the desired package is downloaded.
Another example: I tried to use microsoft.powershell.5.1.referenceassemblies once. Here are the packages that got downloaded:

I have a bunch of packages in my NuGet cache directory that I never used (knowingly), but whose IDs are all prefixes of packages I did use:
This also looks like this is the reason why it takes so long for IntelliSense to work for the package I try to use.
Related information
Provide any related information (optional):
- Operating system: Windows 11 23H2
- Editing Tools: VS 17.12.3
Repro steps
Ctrl + N in Visual Studio and select F# script
Add
#r "nuget: ini-parser"to the fileIt's important to type this into the file instead of pasting from the clipboard.
Observe
C:\Users\...\.nuget\packagesExpected behavior
Only
ini-parserdirectory should appear.Actual behavior
The following directories appear:
in/1.0.0/ini/1.0.7/ini-parser/3.4.0/Every package on nuget.org whose ID is a prefix of the desired package is downloaded.
Another example: I tried to use
microsoft.powershell.5.1.referenceassembliesonce. Here are the packages that got downloaded:I have a bunch of packages in my NuGet cache directory that I never used (knowingly), but whose IDs are all prefixes of packages I did use:
This also looks like this is the reason why it takes so long for IntelliSense to work for the package I try to use.
Related information
Provide any related information (optional):