issue using nuget package from FSI #44

Activity

1. rkosafo commented on Mar 29, 2019

   

   rkosafo

   on Mar 29, 2019

   Contributor

   More actions

   I'm unable to reproduce the error with a normal project in VS2017. Not using paket though. Which versions of the libraries are you using?

   I tried the following

   • Create new .net project
   • Added: Rezoom.SQL.Provider.TSQL. It installs the previously stable version of the library.

   There are problems using the most recent version of the library.

   For the paket version, how did you set it up so I try reproducing this?
2. rkosafo commented on Mar 29, 2019

   

   rkosafo

   on Mar 29, 2019

   Contributor

   More actions

   

   Above are the libraries installed in my test .net project. Please do confirm yours.
3. smoothdeveloper commented on Mar 30, 2019

   

   smoothdeveloper

   on Mar 30, 2019

   CollaboratorAuthor

   More actions

   paket.dependencies

   source https://www.nuget.org/api/v2
   storage: none
   redirects: on
   generate_load_scripts: on
   
   framework: >= net45 , >= netstandard2.0
   
   nuget Auto9G
   nuget FSharp.Core redirects: force
   nuget LicenseToCIL = 0.3.0
   nuget Rezoom.SQL.Provider.SQLite
   nuget Rezoom.SQL.Provider.TSQL
   nuget Rezoom.SQL.Provider.Postgres
   

   paket.lock (relevant snippets):

       FParsec (1.0.3)
       FParsec-Pipes (1.1.1)
       FSharp.Core (4.6.2) - redirects: force
       LicenseToCIL (0.3)
       Npgsql (4.0.5)
       Rezoom (1.0)
       Rezoom.SQL.Provider (0.7.2.40976)
       Rezoom.SQL.Provider.Postgres (0.7)
       Rezoom.SQL.Provider.SQLite (0.7)
       Rezoom.SQL.Provider.TSQL (0.7)
   

   after paket install it will generate the files under .paket/load/* that makes it easy to pull all the dependencies from scripting environment.

   I'm anyways able to work around, and expect things to get sorted out with recent dotnet SDK and TP SDK.