Quick setup with Paket and .fsx scripts

Quick setup with Paket and .fsx scripts

Paket is a dependency manager. It is useful especially when you want to develop .fsx files where the full path of the dependencies are hardcoded in your script. It makes it easier to manage dependencies compared to Nuget because the version of the library isn’t included in the path.

This post will show how to setup a new .fsx file with dependencies handled by Paket.

Initialize Paket and download libraries

Download paket.boostrapper.exe from here. Place it under \.paket and run it:

.paket\paket.bootstrapper.exe

It will download the latest version of paket.exe. Now run init to initialize paket for your solution:

.paket\paket.exe init

Your solution is now ready to get the libraries. Now to install a library run:

.paket\paket.exe add project TestProject nuget MathNet.Numerics.FSharp

project is used to specify a project and nuget is used to specify a nuget package to be downloaded. After running the command, you will now have MathNet.Numerics in your packages folder and you will be able to reference it from your .fsx script files.

#load @"..\packages\MathNet.Numerics.FSharp\MathNet.Numerics.fsx"

open MathNet
open MathNet.Numerics.LinearAlgebra
open MathNet.Numerics.Statistics

let x = vector [ 2.0; 5.0 ]
let y = matrix [ [ 1.0; 2.0 ]
                 [ 3.0; 4.0 ] ]

let z = x * y

When I started F#, I was confused by #I, #r and #load. I also didn’t really know what to google to look for explanation. Actually the explanation are in F# interactive reference here and this is what the directives do (copy pasted from msdn):

  • #I: Specifies an assembly search path in quotation marks.
  • #load: Reads a source file, compiles it, and runs it.
  • #r: References an assembly.

In our case, MathNet.Numerics came with a MathNet.Numerics.fsx" which contains all the references needed to use the library so we just need to load that script.

If MathNet.Numerics have updates, you just need to run the update command and your packages will be updated. Your script files won’t need to be changed.

.paket\paket.exe update

Conclusion

It is very easy to manage dependency with Paket. And I’ve showed you how to quickly and easily add dependency when you just want to hack things in a .fsx file. There is much more that can be done with Paket, you can convert a Nuget solution to Paket, you can also reference git depedencies, git gist, even http dependencies like fssnip for example. All this can be found in the doc. Thanks for reading!

Comments

Post a Comment

Popular posts from this blog

Microsoft Orleans logs warnings and errors

Microsoft Orleans logs warnings and errors Microsoft Orleans is a framework which helps building distributed system by implementing the actor model together with the concept of virtual actors, taking care of availability and concurrency. If you are unfamiliar with Microsoft Orleans, you can look at my previous blog post explaining the benefits of Microsoft Orleans . Even though Orleans promises to abstract the distributed system problems, there are instances where errors arise without us being able to understand what is going on. Lucky us, the logs are well documented… but only for those who can decrypt them. Today I will go through some of the errors and warnings which can be seen from silo and client so that you too can undestand what is going on. Enjoy! The code used to produce those errors can be found on my GitHub https://github.com/Kimserey/orleans-cluster-consul . 1. Client logs Logs on client appears with address {ip}:0 . 1.1. Can’t find implementation of interface An un...
Keep reading

A complete SignalR with ASP Net Core example with WSS, Authentication, Nginx

SignalR with ASP Net Core SignalR is a framework from ASP NET Core allowing us to establish a two way communication between client and server. This two way communication allows the client to send messages to the server but more importantly allows the server to push messages to the client. SignalR makes use of Websocket when available else it falls back to SSE or pulling. Today we will focus on how to setup SignalR to work with WSS, Websocket secure and how we can authenticate the user requesting to connect to our SignalR hub via Webscoket. Getting started with SignalR SSL encryption for Websocket Secure WSS Websocket Authentication with Identity Server 4 SignalR behind Nginx 1. Getting started with SignalR The Hubs are the main components of SignalR. It is an abstraction of a two way communication available for both client and server. Public functions from the hub can be called from the server code and can be called from the client. The frontend NPM package @aspnet/signalr ...
Keep reading

SDK-Style project and project.assets.json

SDK-Style project and project.assets.json Last week I encountered an issue with MSBuild while trying to run it from command line. The issue did not appear when using VisualStudio right click + build but only appeared when using msbuild.exe CLI directly with a clean project. Assets file 'C:\[...]\obj\project.assets.json' not found. Run a NuGet package restore to generate this file. When I first saw the error, few questions came to my mind which I will share today in 3 points: Overview of project.assets.json Slim SDK-Style project Mixing SDK-Style project and old projects Special shoutout to @enricosada who provided me with all the answers regarding the SDK-Style project. 1. Overview of project.assets.json project.assets.json lists all the dependencies of the project. It is created in the /obj folder when using dotnet restore or dotnet build as it implicitly calls restore before build, or msbuid.exe /t:restore with msbuild CLI. To simulate dotnet build (re...
Keep reading