In this post we will see how to use F# scripting to download the daily Bing wallpaper on Windows or Linux.
It is basically a simple application of the F# JSON Type Provider.
Complete source code from this post.
Exceptions are bad.
Not only do we have to remember to catch them everywhere, they also provide a second implicit exit strategy for functions, similar to the
However, there is an alternative more explicit approach.
In this post we will go through an example of how to implement decent functional error handling in F# without using NULL or exceptions.
F# type providers are just awesome because they help to write very efficient and reliable code.
In this post I will show this by implementing a simple, but real-world-like scenario with some F# type providers.
Type providers provide the types, properties and methods to get access to external data sources of various kinds without having to write a lot of boiler-plate code. This makes coding very efficient.
Additionally they offer static types that represent external data and that the compiler will check at compile time. This makes coding very reliable.
So let's look at the scenario that we are going to implement...
Continue reading →
If you want to access a relational database from an F# (or C#) application, SQL F# type providers are commonly used. SQL type providers will provide all the types, properties and methods needed to access and interact with the tables of a SQL database, without having to write any extra boilerplate code. Everything is type checked and if the actual database schema gets out of synch with the database related code, compilation will fail. This is very valuable because it gives you high confidence in the application's data access code.
So at compile time the database has to be up to date and accessible. But how does this work in a continuous integration environment? Off course an option is to have the connection string of the type provider point to a development database on the network. Another solution would be to manually create or update a database on the build server before the build. But I don't really like this because I think the build server should be independent and self-sufficient. A solution to this scenario, that worked for me, is to deploy the database during the build process using Visual Studio database projects and FAKE - F# Make.
There might be other and maybe better solutions that I haven't come up with. I'd be curious to find out. Actually this might be one. The approach that I used, however, works out nicely, so I will give a quick walkthrough on how to set things up.