Comment system on static sites with dotnet core and Github actions

When designing the new blog I finally decided to replace the comment system previously provided by disqus with a much leaner one.

I played around with several options like staticman, but I was never really convinced to adopt any of them. So I thought why not build one myself?

Most of the tools use git issues, some proprietary database or are using jekyll's data file features and commit directly to the repository.
This is not an issue per se, but I like to have data separated from the content in the repository.

I came across a library called Appy.GitDb that uses git as a key value store. I thought this was a perfect use case for this library, so I gave it a shot and came up with what I believe to be a simple, but also a powerful and robust solution.

Working with the community and launch of the new design

I've worked hard the last couple of weeks getting my new design out there and today is the day!

Fixing an N+1 performance problem in XAF/XPO with totally undocumented APIs

We all know (or not) that using an abstraction over any kind of datasource can lead to performance problems. That's nothing new and is quite common with ORMs.

Tasty - Delicious dotnet testing

I want to share some insights on a project I am working on for the last couple of months. I had the idea for the project when working at Ranorex. So what is this, and why you should care.

Install a blazor app as globaltool and service

The year is almost over, and I hope you had nice christmas holidays! I did relax a little bit, but as maybe some of you know I'm working hard on getting Xenial alive. For those that don't know what Xenial is - stay tuned, there will be a announcement around end of january - However, I'll tease a little screenshot right now.