They are eating their own dog food

The built-in build/release tasks of TFS Azure DevOps have manifests, too. And those manifests are right there in the database!

Punished for spelling out

Amazing discovery/public service announcement of the day: between v15 and v16 of the Azure DevOps' .NET client API, the definition of GitHttpClient and its base (where most of the methods are) underwent some changes that might be breaking.

Apples are case sensitive, oranges are not

 Amazing discovery of the day: JSON parsing in SQL Server is kind of case sensitive.

I want to break free

Sometimes, one has release tasks in Azure DevOps (formerly known as TFS) that don't complete synchronously.

NET within NET

Amazing discovery of the day: you can host .NET 5+ within a .NET 4 application.

Full circle with a gap at 11 o'clock

Some time ago I've claimed that I've run a full circle on a TLS certificate lifecycle. Well, there was one more kink in that circle that I've failed to acknowledge at the time.

No version is technically a version

 Amazing discovery of the day: if your Android application doesn't link against the Google Play billing library, but claims to use the com.android.vending.BILLING permission in the manifest, the Google Play developer console will turn your APK down, saying that it uses an unsupported version of the billing library, and why won't you upgrade to v4.

If your app links against billing v5 (the latest as of the time of this writing) but lists said permission in the manifest, you will receive the same error message.