I’m really looking to .NET Net Conf, particularly as I’ll be one of the speakers!
.NET Conf kicks off on 23rd September 16:00 UTC / 24th September 01:30 +930. It’s a virtual conference where all the speakers appear online.
I’m presenting a talk on new publishing options for .NET Core 3 apps. If you’d like to see me live, tune in on 25th September 04:00 UTC / 13:30 +930
We’re also hosting an Adelaide local .NET Conf event next month as part of the Adelaide .NET User Group, with David Wengier speaking about Pragmatic Performance. Sign up here.
It was first announced a few weeks ago, but it deserves a mention here too - DDD Adelaide 2019 is happening on Saturday 23rd November!
Andrew Best (Principal Consultant at Readify) has taken the organisational initiative and I’m exciting to be working with him to bring a day-long conference for all software developers to Adelaide.
Long-time readers may remember we have actually had some events in Adelaide before. Indeed I blogged about the last DDD way back in 2011. In the intervening time, DDDs have been happening all around Australia. Melbourne, Sydney, Brisbane and Perth are all now running annual DDD conferences. They’ve grown to become significant events (many selling out within hours of tickets being made available!), and some now regularly have 700-800 attendees (big enough that they have to book a proper convention centre for their venue).
So the DDD we’re putting on this year is going to be a little different to anything that has ever happened in Adelaide before. It’s going to be bigger and better (with two tracks), and is open to any and all software developers (plus related fields) and any programming language, technology, ecosystem, cloud, little and big-endian!
While we’re not aiming to be quite as large our interstate cousins, I think if this year’s event is well supported by the local developer community, then the only way is up for the future.
DDD is run as a non-profit event. So while we are charge for registration, this covers the cost of providing catering for the day. There’s other costs with running DDD, so it’s great to have some big-name sponsors also supporting us. In fact there’s still room for more sponsors to get on board.
So what happens between now and November 23rd?
Registrations are open now. Sign up to attend now!
The Call for Presentations closes at the end of Wednesday September 4th. If you’ve got something you’d be prepared to present to a group of interested people, submit it now!
The following week (12th September to be precise), the full list of proposed sessions will be published for registered attendees to vote on. Yes, the people who are going to attend get to vote on which sessions they want to see. Yet another incentive to register.
After voting closes (27th September) and we’ve confirmed presenter availability then the final agenda will be published (3rd October).
So sign up and I’ll see you on the 23rd. It’s going to be awesome!
Topshelf is a useful library if you have a .NET application that you would like to easily turn into a Windows Service.
A common approach is to create a console application, wire in Topshelf and then you can run it as either a console app or install and start it as a Windows service.
One thing I encountered this week was that by default Topshelf changes the current directory to the location of your .exe when your application runs. This makes sense because otherwise the default current directory for a Windows service is actually
c:\windows\system32! If you’re trying to load additional files from the same directory as the .exe then that’s not where you’d want to be looking so Topshelf’s alteration makes sense.
But what about for debugging?
In Visual Studio, when you press F5 to debug a web project (which is the kind I was working with), the current directory defaults to the project’s directory. Again you may have logic that makes assumptions about other resources that need to be loaded relative to the project directory - if you’re now using Topshelf that’s going to break as the current directory will be changed. How to fix this?
Stepping through the Topshelf source code, I realised that I wanted a version of
ConsoleRunHost that didn’t have the calls to
Directory.SetCurrentDirectory(). That class is instantiated by the
RunBuilder class, which in turn is returned by the
DefaultHostBuilderFactory method in
So that’s the default factory, but the same class also provides a
UseHostBuilder method that allows you to provide your own factory instead. That’s just what I needed.
By adding my own factory method that returned an instance of my own custom RunBuilder, which then returned a custom ConsoleRunHost implementation that was identical to Topshelf’s ConsoleRunHost with the exception that it didn’t change the default directory.
private static HostBuilder HostBuilderFactory(HostEnvironment environment, HostSettings settings)
return new MyRunBuilder(environment, settings);
And tell Topshelf to use this method by calling
var rc = HostFactory.Run(x =>
If you wanted to, you could even check if you were running under the debugger to decide whether to use the default or custom behaviour.
It’s nice when libraries have thought about extensibility and provide hooks for consumers to swap in custom logic.
This year I decided to return to playing basketball socially after a break of about 5-6 years. Like most other sports I’d tried, I didn’t have much natural talent, but enjoyed participating.
This season did not start out well. The first game back, I was enjoying being back on the court (if also realising how unfit I was!). But as the match progressed, my heel was getting sorer and sorer. Later diagnosed by the Physio as tendonitis - probably caused by going out way too hard after such a long time of not running at all.
A week off and some daily stretching (that I’m still doing months later) and I was feeling ok to get back again. A few more games and then more problems..
My back had been feeling a little uncomfortable earlier in the day, but I figured lots of stretching and I’d be fine. I played with out any issues and then drove home. But as I got out of the car, I felt my back go!
Some Chiro on the Monday, more stretching and trying to stand (instead of sitting down) at work meant, after another week off, I thought I’d be ok to come back again. I played last week without incident, though I was a little sore the next day.
Yesterday, my back was still not 100% but I figured I’d see how I went. That was probably a mistake. Part-way through the second half of the game, I went to chase the ball and felt my back go again. I took no further part in the game. Time to listen to my body and give it a proper rest.
And that’s how my 2019 basketball season unceremoniously ended. Maybe I can give it another go in 2020, but if I do I think I’ll need to invest in a lot better preparation. It would be disappointing if it turns out that I can’t play again, but that’s also a possibility. And better to retire my basketball boots and still be able to do other things, than really injure myself badly.
This error caught me by surprise today:
C:\dev\git\project [feature ↓1 ↑2 +1 ~0 -0 !]> git push --force-with-lease
Enumerating objects: 22, done.
Counting objects: 100% (22/22), done.
Delta compression using up to 8 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (12/12), 1.61 KiB | 824.00 KiB/s, done.
Total 12 (delta 6), reused 8 (delta 4)
remote: Analyzing objects... (12/12) (8 ms)
remote: Storing packfile... done (115 ms)
remote: Storing index... done (81 ms)
! [remote rejected] feature -> feature (TF401027: You need the Git 'ForcePush' permission to perform this action. Details: identity '93086622-abb9-4886-b994-502e7f2afc21\[email protected]', scope 'branch'.)
error: failed to push some refs to 'https://mytenancy.visualstudio.com/repo/_git/project'
I was trying to push a change to a Git branch in Azure DevOps Repos. I’d just done an interactive rebase to update history on the branch and was trying to force push my changes - something I’ve done countless times before.
Reviewing the permissions for this repository, the Force push (rewrite history, delete branches and tags) permission was Not Set (eg. neither explicitly allowed nor denied). Checking other projects and repositories, this was also the case, so what’s different?
Well one thing that’s different is that I didn’t create this branch - it was created by another developer. Force pushing to a shared branch is generally frowned upon (as if it isn’t coordinated it can cause all kinds of problems), and so it seems DevOps helps guard against this problem by defaulting to granting the Force Push permission just to the branch creator (and also to users who are the Project administrator - as set in the Project details page of Project Settings).
Because I didn’t create the original branch and I was not a project administrator in this particular project, no push for me!
Check out the descriptions of the different permissions for Git repositories and the default Git repository and branch permissions.