Technology Idiocy Log

Although I've mostly retired from software development, I'm still doing a few hours of maintenance and debugging each week for old products. In my previous post about easing into retirement, I mentioned many examples of random idiotic wildly counterproductive things keep going wrong and suck all enjoyment of working in IT. Idiotic things are still happening, and this post is a growing log of recent idiotic problems related to IT and technology in general that I can show to friends and colleagues as proof of how "everything f***ing doesn't work".

---

March 2025 — T4 Templates in .NET Core PENDING (3 hours)
If a T4 template in a Visual Studio project attempts to "touch" a .NET Core Assembly it will fail with reference errors. This wouldn't normally happen, but in my case I was dynamically loading an Assembly so I could reflect over it and generate code. The Assembly was recently changed from targeting netstandard20 to net80, so I hit the problem.

A moderised TextTransformCore.exe was released in June 2023, but they state that in-IDE or MSBuild tasks are not supported yet, and after an hour of experiments in March 2025 I sadly confirm that it's still a limitation. Therefore the only viable technique remaining is to use the tool from a command prompt to manually process the .tt file. You can't have $(ProjectDir) style variables in the .tt file because there is no way for the tool to resolve their values (using <T4ParameterValues> doesn't work). My bat file in the solution folder looks like this, and it uses the ‑r switch to tell the processor where the dynamically loaded Assembly is found:

"%ProgramFiles%\Microsoft Visual Studio\2022\Professional\Common7\IDE\TextTransformCore" MyTemplate.tt ‑r bin\Debug\net8.0\MyAssembly.dll

I pray that they will integrate the new T4 tool into the VS IDE and build processing soon, but I'm worried that Microsoft will put more effort into urging people to use Rosyln Source Generators instead. As I say in my C# Compiler Source Generators post a few years ago, writing generators is fragile, tedious and complicated compared to knocking-out a .tt file.

March 2025 — Publish Blazor App SOLVED (4 hours)
I need to publish a Blazor app with small changes to match those in a web service it calls. The project fails to compile due to a missing project.assets.json file. An hour of web searching for a fix produces a dozen suggestions that are either nonsensical or have no effect. Cleaning folders, restoring packages and workloads, etc, nothing works (and some ran for 20 minutes). It looks like some net60 environment change in my work PC has broken the build process. Out of desperation I upgrade from net60 to net80 and update all the packages and publish settings to match. Now it compiles and runs, but publishing still fails. I eventually see a clue: the following workloads must be installed: wasm-tools-net8. I run the command dotnet workload install wasm-tools-net8 and restart Visual Studio, now it publishes.

March 2025 — Update Chrome SOLVED (1.5 hours)
I try to install Adblock Plus in Chrome on my work PC and it says that Chome is too old. I attempt to update Chrome and it fails with some hex code ending in 2. The update is repeated a few times with several elevation prompts (which seem to work), but the error is unchanged. I login as local Administrator, which for some reason causes 2 minute pauses between logoff and logon. Update continues to fail. I download the Chrome installer and run it, and the update seems to work, with only one elevation prompt. I restart Chrome and it requests another update, which luckily this time downloads and installs without error. I log back on as my regular user (after a 2 minute stall black screen) and start Chrome and my home page fails to load because all the network shares are dead. I reboot and now Chrome seems to be updated and working normally. Now I can install Adblock Plus, which also removes the garish ads plastered by default all over popular news web sites.

March 2025 — PC Speakers fault FAILED (1 hour)
The small Logi z213 speakers on my wife's PC stop working. After an hour of experiments I determine that the wire inside the sealed plastic on the stereo jack is loose, as wiggling it around causes the sound to stop and start. The right speaker is stuck on half volume. This is a classic case of an SPF, a Single (Stupid) Point of Failure that can't be repaired and it renders the whole device practically useless. The $70 speakers only lasted about one year.

February 2025 — Visual Studio 2022 Licensing SOLVED (5 hours)
Azure Storage Explorer was telling me that some accounts needed reauthentication, which I did and it seemed to work. About an hour later I launch Visual Studio 2022 and it tells me that my trial period has expired. I spend an hour entering my usual credentials over and over and over, but the problem remains unchanged. I notice that the account dialog says: This product is licensed to: wrong address. For another hour I search for how to change the license address, or cancel it, or do anything useful. The next day, with a fresh mind I bumble into a fix by changing the Account Options > combo Windows authentication broker to Embedded web browser, relaunching VS, entering my credentials again, which causes everything to come good and the Accounts screen is sensible and shows no alerts. I then revert the combo and relaunch VS, which causes more authentication prompts, but they are also finally satisfied and all problems are solved with the original settings restored. By looking at some files in %TEMP%\servicehub\logs I see Could not find a WAM account message which lead to This Community Issue which is solved using exactly the same workaround that I used by dumb luck.

February 2025 — Dynamic C# Source Compile SOLVED (3 hours)
in July 2014 I posted an article titled Dynamic C# code compilation where I use the CSharpCodeProvider class to compile C# source code at runtime, then invoke a method inside the generated Assembly. Unfortunately that technique only works in the full .NET Framework and is deprecated in .NET Core. I went looking for modern equivalent code so I could udpate the post. After two hours of searching I found several samples that all did not work for various reasons, even the MSDN sample code produced a PlatformNotSupportedException, and the docs confusingly confirmed that was expected for .NET Core 2+. I eventually found some (non working) sample code that used the CSharpCompilation and related classes, which I tweaked and almost worked. It produced compile errors like Predefined type 'System.Object' is not defined or imported because the basic references were not found. I eventually found the minimum required references to make the compile work. For more information see Dynamic C# Code Compilation.

January 2025 — PC Sound Problems SOLVED (2 hours)
Playback through the line-out stops working and only the speakers in the screen work. All sound recording stops because Audacity says there are no input devices. After an hour of inspecting Windows settings and cables I discover that the power cable and another have been pulled out of the small mixer out of sight behind my screen. I think a cat got stuck behind my desk and got tangled in the cables trying to get out. I put all the cables back and reboot. Playback now works, but not recording. I stuff around with more settings in Windows and Audacity and after more than an hour of random stuffing around the recording device is visible and I can select it and recording works again.

January 2025 — TV Sound Problems PENDING (2 hours)
Our LG 55" TV only has two ways of playing sound: (1) HDMI-ARC which is typically used with a sound bar or similar (2) Optical out plug. We don't own a HDMI-ARC compatible playback device, just a $99 set of 5 speakers which have worked pleasantly for over 20 years using their ancient RCA plugs. Luckily, the cheap speakers have an optical input, but connecting it to the TV's optical out produces no sound. I have no way of determining which part is failing. We have no choice but to eventually buy a sound bar or something similar, but they cost anything from $200 to $2000 and it's just a burden of brainpower and money to choose something.

January 2025 — .NET 9 Upgrade SOLVED (3 hours)
Since .NET 9 had been out for a few months, I decided to bulk upgrade my main hobby suite named Hoarder from .NET 8 to 9. I did this purely as an academic exercise to keep up with the latest versions of everything and play with them. The upgrade wizard went through all 10 projects (including a Blazor one) and produced only a few low-level warning messages. The solution compiled okay first time. At runtime everything was working until I got to the WPF desktop program which died with an incomprehensible Exception deep inside the CodePage loading library. There were no matching results from web searches and I fiddled around for ages without success. I had run out of ideas and give-up in disgust. Six weeks later I revisited the problem, hit run on the WPF program and it ran perfectly. I don't know what was wrong and I don't know what went right.

Orthogonal Programming

Easing into retirement

I posted the following message into the ozdotnet mailing list in October 2024.

---

Hello everyone, I have an announcement and tale that might interest you.

I’m easing into retirement.

Companies I’ve been working for are being sold, retired or are no longer developing new software. I only have a few hours of ad-hoc maintenance work each week. Running out of legacy work would drive a regular dev to seek new work, but in my case, I declined to create a LinkedIn page, or send out feelers through contacts for new work, because… I’m burnt out.

Why? That’s what pleases me to imagine might interest you.

I learned to code in 1975 and became an official programmer in 1981. I wrote FORTRAN, ALGOL, COBOL, assemblers and various JCLs and scripting languages on Honeywell, FACOM and IBM mainframes. Things were simpler back then of course because you moved inside the ecosystem of a particular manufacturer and had high-level support and voluminous and accurate documentation. If you wanted to solve a problem or do something edgy, then an answer was nearby. It was a different simpler world, but … everything worked.

Now, well into the 21st century of IT, everything doesn’t work. My wife often hears me shout from the other end of the house “Everything f***ing doesn’t work”. I also only semi-jokingly say I’ll have these words carved into my gravestone: “Everything f***ing doesn’t work all the f***ing time”.

Overall, what has burnt me out is complexity and instability. I’ll break those topics down a bit.

Everything in modern IT is complicated and fragile. Every new toolkit, platform, pattern, library, package, upgrade, etc is unlikely to install and work first time. I seem to spend more time getting things working and updated than I do actually writing software. In a typical working month I might have to juggle Windows, Linux, Android, iOS, macOS, Google, Amazon, Azure, .NET, Python, PowerShell and C++, and they all have different styles and cultures. Software engineering has fractured into so many overlapping pieces that I’m tired of trying to maintain competence in them all.

That leads naturally to the problem of dependencies. Just having so many moving parts with so many different versions available produces dependencies more complex than abstract algebra. How many times have you hit some kind of compile or runtime version conflict and spent hours trying to dig your way out of it? (A special salute to Mr Newtonsoft there!) Or you install A, but it needs B, which needs C, and so on.

I often hit incomprehensible blocker problems for which web searches produce absurd and conflicting suggestions which don’t work anyway. All I can do is futz around and change things randomly until things work again. I don’t know what went wrong and I don’t know what went right.

The Web — Browsers, HTML, CSS, JavaScript, the HTTP protocol, JSON and REST can all burn for eternity in fusing hellfire. About ten years ago I told my customers I refused to write any more web UI apps. However, I was forced to do so a few times and I’m still scarred by the horror. It’s just over 30 years since the web became public and we’re still attempting to render serious business apps using dumb HTML. HTML5 is the joke of the century (so far). I still lament the loss of Silverlight.

Git — Someone is lucky I don’t own a gun.

Fads — An exercise for the reader: name all the platforms, kits, patterns and frameworks that you know were once the coolest thing and now might only be found in history articles. An advanced exercise is to speculate on which currently cool things will be gone soon.

Finally, here is a list of typical things that give me the shits, just as they pop out of my head.

• Attempting to compile projects that have been idle for a year or more will usually fail due to changed dependencies or deprecations and it can take hours to get them going again.
• I develop and test something with great care, then deploy it and it crashes. This is part of the general “it works on my machine” disease.
• I can stop successful work on Friday night, then resume on Monday morning and everything utterly fails.
• My USB microscope and music recording both stopped working recently, and it took me a week to discover that it was a block by Windows 11 app security (I thought it was hardware or incompatibility problem).
• Security! Walls, barriers and hurdles of security everywhere to crash through. Yes, I know we need security everywhere to stop the black hats, but it’s also stopping developers. Lord knows how many times I’ve hit run or debug on my own PC and I get “Access denied” and hours of research will be required. I’m also fed-up with ceaseless 2FA requests via email or SMS.
• Everything about mobile devices. The ludicrous variety of devices and brands makes app development a nightmare. Then you must struggle through the variety of publishing processes.
• My final entry is simply the tiny “thousand cuts” that torture you during development: version mismatches, inconsistent behaviour, strange errors, editor quirks, missing files, etc. All the little personal problems that slip between the cracks of bigger issues I’ve previous mentioned. Your mileage may vary.

In summary, being a software engineer is now so exhausting that after 40+ years of a generally enjoyable career immersed in programming and computer technology I’ve reached a point I never thought would arrive… I’m burnt out. Even working on my hobby projects has become a burden because they suffer from many of the impediments previously mentioned.

I still plan to attend some upcoming conventions and Meetups, and I’ll be watching the forum, but my posts will diminish because I’m probably out trying to prevent the garden and house disintegrating back into the earth from whence they came.

Greg Keogh

Orthogonal Programming

Web API Status Codes and Errors

Overview

This post is an update to one I made in 2018 which complained about the clumsy way REST style web services use status codes to report success or failure for various types of requests. The key point I'm going to make is that the convention of using status codes like 201 (Created), 204 (NoContent), 400 (BadRequest), etc, is inappropriate for expressing the results from a typical business service.

The list of HTTP Status Codes contains a bewlidering set of values that are mostly related to networking, or web server internals or other esoteric conditions. There is no sensible mapping of these status codes to typical business processing results. You could argue that a 400 (BadRequest) might indicate a bad parameter in a request, but the definition of 400 is far broader than that. If you get a 404 (NotFound), then exactly what is "not found"? Is it some file or database row, or the whole uri? Many other status codes are event trickier to assign some sort of business meaning.

The worst thing about the zoo of possible response codes is that the client has the burden of switching code paths to handle them all, and hoping they haven't missed any. Polite service authors will publish OpenAPI to document all their responses, but it can be time-consuming to safely turn large amounts of documentation into code (although there are various tools that convert OpenAPI into client-side code).

Only 200 (OK)

I eventually got fed-up with thinking about status codes and decided to return only 200 (OK) from my services. This indicates that the request succeeded without any kind of external problem. It does not indicate if the request succeeded in the business logic sense, as some extra standard information in the response body provides that information (explained shortly).

Any response code other than 200 indicates something went seriously wrong unrelated to the service logic, probably a network or web server failure. In this case the client app would probably show a pink screen or similar to indicate a serious problem.

If your service only returns 200, then how do you indicate if the business logic of the request succeeded or not?

I think the simplest way of returning business processing result information is to have some standard properties present in every response. Here is part of a typical error response from one of my services:

{
  "code": 2,
  "title": "Customer create failed",
  "detail": "Customer with key '806000123' name 'Contoso Pty Ltd' already exists.",
  // See below for more details of what could be here...
  "data": null  // Success data would go here
}

Exactly what standard properties to place in the response is your choice, and there are many articles that argue around this matter. In recent years there have been attempts to standardise error reporting properties, such as RFC 7807. The full RFC error response recommendations may be overkill for most business scenarios, but it's worth considering following some of the naming conventions.

Coding Details

What follows is specific to the C# language, but it can easily be applied to any other modern language.

There are two ways to return standard response properties. Firstly, define a base class with the properties and derive all responses from the base class. This does cause the standard properties to merge into the response properties at the root level, which might look a bit confusing. Secondly (my preference), is to have a generic response class like this:

public class ResponseWrap<T>
{
  public ResponseWrap(T data)
  {
    Data = data;
  }
  public ResponseWrap(int code, string? title, string? detail = null)
  {
    Code = code;
    Title = title;
    Detail = detail;
  }
  public string? Title { get; set; }
  public string? Detail { get; set; }
  public bool HasError => Code != null;
  public int? Code { get; set; }
  public T Data { get; set; }
}

Note how the standard properties are at root level, and so is a Data generic property which is expected to contain any data that is in a success response. This results in a simply shaped JSON document common to all service responses. Clients can inspect the HasError property to determine if the business logic of the requests suceeded or not. The exact code is flexible and can be adjusted according to coding preferences, but the important fact is that there are some root standard properties and one of them indicates success or failure. In case of success, the Data property will contain the return data and the other root properties will be null, and in case of failure the reverse is true.

Returning values from service methods will be easier as there is no need to construct different response status codes and types. The pair of constructors of the response class simplify service code to look like this:

if (cust == null)
  return new ResponseWrap<Customer?>(2, $"Customer {id} not found", null);
else
  return new ResponseWrap<Customer?>(cust)

.NET Web API Global Errors

Unhandled errors in a .NET Web API controller will result in a 500 (InternalServerError) and a response body that doesn't contain any useful diagnostic information. In .NET Core services you can use a global exception handler to trap unexpected errors and convert them into the standard response so that clients always receive the same shaped JSON response bodies.

This is entirely optional, as letting the error propagate back to the client as a status 500 will clearly indicate to them that something went seriously wrong, and the response body might be irrelevant anyway. The service should have internally logged the detailed error details so that developers can diagnose the problem.

Summary

By reducing the REST responses down to a single status code and putting standard properties in the response, it could be argued that I'm hijacking the REST conventions and turning them into a toy protocol. I can't argue with that, but as a developer I really need a simple protocol to return only success or failure information without the mental bother of applying status codes to my business logic (where that's meaningful). It also simplifies the coding on the service and client sides.

Ironically, the .NET SOAP protocol I used back in the 2000s was actually similar to what I'm doing now. I'm conforted to know that I'm not the only person who has considered ignoring status codes, as I recently used the API of a parcel shipping company who only returned status 200 and they had a root property named code in all their responses to indicate success or failure. In their case, curiously, code=300 indicated success.

Orthogonal Programming