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.

One of the questions I’ve started asking myself is what makes for happy C#? After a few years getting a bit more understanding of ML like languages like F# I’ve started to realise that C# is not built to write the kind of code that you write in an ML. Instead, you are happier when you embrace the Ruby-like patterns in C#. If you look at C# sort of like a typed Ruby like language: Object orientation, mutability first and meta programming using reflection. When you see that this is shared between the two lan[...]

One of the questions I’ve started asking myself is what makes for happy C#? After a few years getting a bit more understanding of ML like languages like F# I’ve started to realise that C# is not built to write the kind of code that you write in an ML. Instead, you are happier when you embrace the Ruby-like patterns in C#. If you look at C# sort of like a typed Ruby like language: Object orientation, mutability first and meta programming using reflection. When you see that this is shared between the two lan[...]