This is my preference as well. Syntax can be googled, internal business process and reasoning cannot.

I've noticed this too. It's nearly impossible to get windows to have borders that are clearly visible. I really don't understand how this makes windows more usable...other than I've also noticed that many people never learned to use Windows and just full screen EVERYTHING.

My advise is to find out how it's supposed to work, then get a Click PLC from Automation Direct and re-implement it.

Personally, I ditched the multi-monitor setup for "one big monitor" a few years ago and haven't looked back. Especially on Windows since snapping easily lets me use my monitor as it it's two just by smacking the windows against one of the sides. I have a 43" LG 4K monitor and it's freakn' awesome for getting work done. I wouldn't recommend it for gaming or even watching movies from your desk. When I use it with my Mac, I have do to some re-sizing, but it's not too bad.

I hadn't looked into it, but perhaps I should!

I hear you! I'm one of those rare folks that like the VB.net/WPF combination. I actually went from VBA to VB.net and pretty much skipped classic VB all together. I've never understood how C# became the defacto MS language other than it's [only slightly] less verbose. The case sensitivity in C# is the thing that really makes me not want to use it...Of course, this is just my humble opinion. I'm sure there are reasons that C# works better for others. But with all that said, these days I'm in a role where I don't do any coding, and with the current software development landscape, I'm pretty okay with that.

but then there's the DPI issue, which is the main reason I started to work more with WPF...then I fell in love with how WPF does databinding (yes, I know it can be done in Winforms too, but it was more of an afterthought and doesn't work quite as cleanly, IMHO)