This. Very much this. Happened to me last week.

Apparently there is a user limit of 55 users. Just got a "session is full" error trying to join. FYI.

This little snippet, right here, decompiled from .NET 4.8. The "Publisher" (read: your code signing cert) is the highest tier of evidence to identify your assembly. Calls to "IsolatedStorageFile.GetMachineStoreForAssembly()" on DIFFERENT assemblies signed with the came cert will collide.

Good morning. Sleep well?

This. All of my this. I watch tutorials at 2x speed, 1.75x if I'm tired, and slower if it's a difficult accent. Makes my co-workers give me funny looks, and our company CEO grin because he likes us to "use our time efficiency!".

Having flashbacks to Robot Unicorn Attack now. Thanks. :D

If you don't have the heartbreak, you can't have the happiness. I believe the happiness a pet brings outweighs the heartbreak of eventually losing that pet.

Is that the 9th iteration of Rabbits I see?

Wish we could use git, but getting our previous manager/dev lead to learn how to resolve merge conflicts was impossible. Now we're stuck with TFS until we can get the time to migrate to git and retrain people.

Okay, yeah, I can see why that it needed in this instance. Wish the mappings/upstream were stored in the mapped folder, like the way git does it. And a proper branching feature, instead of trying to hack shelvesets to do experimental builds.

Tell that to our CEO. Jobs lay fallow until someone asks for a status update or complains, then suddenly our ticket priority queue changes and $CEO is the phone, "why wasn't this done?". My standard response is, "because you didn't prioritize it." It's always the shiny new jobs that get priority.

TFS is the bane of our existance at work. The again, part of that is that one developer who goes "Conflict? I know how to fix this! <take local>". But mapping 2 projects to the same location is *cursed*, lol.

Had to write a system service that spawns a process on the currently active window station. This process searches for a particular window title, and if it sees a new instance of the window, forces a move to the primary monitor. Bug was preventing POS terminals from doing end-of-day process.

Totally agree. Wouldn't need an annoying workaround if the problem didn't exist in the first place. There's another bug on touchscreen kiosks that have a second, non-touchscreen display where sometimes a window will open on the secondary display and you can't move it to primary. No keyboard on them.

I know it's not a fix, but in a pinch it will get you out of trouble.

Hover over the icon on the taskbar to show the window preview. Right-click the window preview. Choose "Move" from the context menu. Press up, then left on your keyboard. The window will now be "snapped" to your mouse and you can move it anywhere. Does not work on tool windows or non-taskbar windows.

Aaah, yeah, if you need a mesh, that's a problem.

As I understand it, Gaussian Splats are extremely good at representing furry and fuzzy objects in photoscans. Maybe giving that a try would yield better results?