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
Describe the bug
Would be nice if resolution path would be inferred by .nuget directory of .fsx script automatically...
also seems #r "nuget: System.Data.SqlClient" is required else the type throws an exception...
To Reproduce
use provider from .fsx script and try reference ngpqslq.dll from current directory
Expected behavior
Would be nice not to need the resolution path when using the type provider from scripts using
#r "nuget : SQLProvider"
Desktop (please complete the following information):
Device: MAC
OS: MacOS
The text was updated successfully, but these errors were encountered:
jkone27
changed the title
MacOs has to pass resolutionPath for NPGSQL.dll
Suggestion - infer resolution path for script scenario .fsx (MacOs) ?
Jun 16, 2022
This is a great idea, but how do we know the path of that DLL? With '#r' the FSI loads the SQLProvider then from nuget cache, but SQLProvider loads Npgsql via reflection, so we'd need to know the path and thus e.g. which version we are loading.
It seems to me that FSI creates some kind of temporary project in some location %home%\.packagemanagement\nuget\Projects\(guid)
Describe the bug
Would be nice if resolution path would be inferred by .nuget directory of .fsx script automatically...
also seems #r "nuget: System.Data.SqlClient" is required else the type throws an exception...
To Reproduce
use provider from .fsx script and try reference ngpqslq.dll from current directory
Expected behavior
Would be nice not to need the resolution path when using the type provider from scripts using
#r "nuget : SQLProvider"
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: