The worst part: shit for documentation. And almost zero online content. LLMs give invalid information that doesn't work. From the looks of it, nobody bothers with this... not surprising. I'm back to getting rid of the SDK integration - it's just not worth the pain as much as I

This is after already spending nearly an hour trying to sync up the runtime dependencies and libraries and versions and restrictions. Plus the overhead of a huge runtime dependency that is larger than the entire rest of the application - for shit that's already built into

It is utter insanity how hard it is to use any feature of the .NET Windows SDK libs in a non-WinSDK project. It's the same crap I ran into months ago trying to integrate speech apis. Which made me toss using it because of this stupidity:

It's really cool when you see people using the documentation you have written.

Last night dinner with friends. Yeah there were left overs 😂

Solution I found was to go into Services and stop all the Hyper-V related services (2 of them). Then re-run. Obviously only reasonable idea if you don't have other things actively running (Docker, WSL).

In case you're unfamiliar - Sandbox is a clean, temporary virtualized Windows environment you can fire up to use for testing software installs or running potentially unsafe code. It's a great tool (that I should be using more often). I use it to test software installs of my

Well - Windows Sandbox worked once today. After that it's just this:

@mkristensen To be clear, the feature is fine as is, even the defaults - the change would be remembering your last setting in the VS solution settings.

Hey @mkristensen - it'd be nice if the Git Commit dialog wouldn't auto-default to All Repositories whenever you restart Visual Studio and remember your last solution setting. While the feature is very useful to commit to multiple repos, most of the time multiple repos just add

Brrrr… Fall is here with the first dusting of snow on Mt Adams. Time to pack it up and head South.

How does it feel living in the relentless Fear Factory thrown at you day after day? I wrote this song during the Covid mania with a totally reversed context in mind, but it works just as well today in the exactly reversed environment. https://t.co/EvDbr7Kbrp

Ironically I've had CoPilot help me with a few related issues here as well as a shot at letting it troubleshoot - the latter made things a lot worse. Total garbage. Claude 4.5, ChatGpt 4.1 & Grok code each with their own variations of the same failure. Probably not just me?

I'm embarrassed to say I've spent a half a day messing with a dialog close operation. Save confirmation, many exit paths (button, window) and async change state detection plus async operations in WPF in events. Not the first time I've struggled with this either. 🥲

What are these people doing to try to open a folder in a \\.\nul path? How is that even possible from a UI operation (directory listing from a folder browser)

Current mood: Ready to get back in the waves on Maui - 3 more weeks to go until we go home.

Looking forward to quiet and cozy evening at our off the grid ‘camp’. It’s turned into less of a camp with the tiny shed we built last year but now that it’s getting cold we’re looking forward to not sleeping on the cold ground 😂

Had a great time chatting with @DanWahlin on Coffee & OSS today about all kinds of #tech topics. Video is live on YouTube and podcast is available wherever you find them. Take a look/listen and thanks! https://t.co/tCtuT7KiE3

Not only that, but the deployment page shows a model release date, which IS NOT the API date, which of course does not show on that very same page. The thing that actually matters and has to be provided you have to figure out by running a sample request and showing the Curl

This shit annoys me no end with Azure AI deployments. You have to specify the api-version or the endpoint will fail. Why is that not optional? Default to the latest api if not provided! And why are these versions always PREVIEW?