posts

As part of a CI process we needed to regularly check for outdated packages for a dotnet solution. This particular solution used Central Package Management.

As part of our migration to Azure DevOps, we needed to consume a private NuGet feed in our ASP.NET application. Now as we had set up our private NuGet feed using Azure DevOps Artifacts previously, we just needed to get Azure Pipelines to use it.

As part of our move to Azure DevOps (from BitBucket and our own hosted Jenkins), we needed to host some internally used NuGet packages (packaged up third-party commercial libraries).

We’re in the process of migrating a long-term project from our in-house build environment (Jenkins on Windows) to Azure DevOps. This is the first in a series of posts documenting our process.

We recently needed to support local functions in runtime C# code. This runtime code is to allow us or the Customer to customise how a HTTP POST JSON document is constructed. At the time we were using CSScript to add runtime scripting to the application, however the default Evaluator was Mono which did not support local functions.

A post on how I configured Jenkins v2 on Windows for ASP.NET Core applications using Pipeline as code.

Hopefully this saves someone some time in the future.

Now that we have Ionide installed, we can do REPL development by using the F# Interactive console (FSI).

Previously I showed how to install F# on OSX. In this post I’ll start showing you how you can start devloping F# in Visual Studio Code on OSX (macOS… whatever).

I’m starting to get into iOS development using Xamarin.

As the title indicates, this is how to install the various bits and pieces to be able to compile F# applications and run F# scripts on OS X.

Instructions that I used to install node recently.

Having had to set up Git in Jenkins running on Windows recently, I thought I’d document what I did to get it to work.