What’s the lure of F#? The main lure of F# is that it’s a surprisingly competent ML style language that transcends some of the limitations of CIL. From my point of view, the main distinguishing feature for F# is Statically Resolved Type Parameters. It’s a feature you don’t want to see in business code (same as reflection in C#), but something that enables libraries to take F# to the next level. Compare this to type classes in Haskell and what is called functors in OCaml. What has delighted me? The e[...]

So what has been my experience using Identity Server? I’ve (and others in my team) have worked on a project using Identity Server 4 since early 2017. What lead us there? The main reason why we started to consider it was due to the main business goals: To have a JWT provider that enables a single page application to communicate with a plethora of micro services To use an existing solutions. The reasoning being that if the company used existing software, that would create a dependency on that softwa[...]

So what has been my experience using Identity Server? I’ve (and others in my team) have worked on a project using Identity Server 4 since early 2017. What lead us there? The main reason why we started to consider it was due to the main business goals: To have a JWT provider that enables a single page application to communicate with a plethora of micro services To use an existing solutions. The reasoning being that if the company used existing software, that would create a dependency on that softwa[...]

After writing the previous post about getting some of the infrastructure working for non Windows, I’ve seen better ways of getting it to work. In particular we have seen the use of netfx.props as seen in FSharp.TypeProviders.SDK. Then you add the following to your csproj or fsproj file: <Project Sdk="Microsoft.NET.Sdk"> <Import Project="..\netfx.props" /> as can be seen in FSharp.TypeProviders.SDK.fsproj.

After writing the previous post about getting some of the infrastructure working for non Windows, I’ve seen better ways of getting it to work. In particular we have seen the use of netfx.props as seen in FSharp.TypeProviders.SDK. Then you add the following to your csproj or fsproj file: <Project Sdk="Microsoft.NET.Sdk"> <Import Project="..\netfx.props" /> as can be seen in FSharp.TypeProviders.SDK.fsproj.