The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I understand what you're saying, but as a developer, if you want to support Windows 10, then as long as you target the lowest common denominator, it's easier to do so than including any previous mix of 8.1/7/Vista/XP/etc.
Is there really any feature in Windows 10 that a dev is relying on that wasn't in the first release?
What you're describing is hardly what MS is doing these days. They're no longer producing huge, monolithic upgrades that take 3 years between releases. They're no longer trashing/redesigning whole areas from scratch. And that's the point Terry Myerson was trying to make. You don't agree with that?
From my side old windows apps always ran on later ones, so no problem there, the issue is which is the oldest you support.
Is that so hard a decision?
Ok, let's take again my .NET example. Newer versions of Windows (not just 10) no longer have 2.0/3.5 pre-installed out of the box, so you may as well commit to 4.[something]. 4.0? 4.5? Newer? 4.0 is out of support. I'm not so sure about 4.5. A quick Google search shows that you're guaranteed that all Windows 10 versions will have at least 4.6, so I'd say it's a good starting point and should remain in support for a good while still.
So I had a 10.1511 and tried to install an 1806 HLK client, it said 'get stuffed'.
Had to look up HLK (Windows Hardware Lab Kit?), but it seems obvious to me that it works like a Windows SDK or a DDK and is tied to an OS release. There was a Windows SDK for Windows 7, and a separate one for 7 + SP1. Installing the newer SDK on the original (pre-SP1) 7 would fail. No surprise then, and no surprise now.
I dunno, just continuing to play devil's advocate here. As much as I'd rather pretend 8/8.1/10 never happened, if I had the choice to support 7/8/8.1 OR "all versions of 10", I'd rather pick 10 as it's a lot closer to being a single, unified OS than 7/8/8.1 are, relative to each other.
All of that said, I can't say I'm terribly happy with the number of Win10 versions there could be out there. I wouldn't mind if they reduced the pace.
ike a Windows SDK or a DDK and is tied to an OS release
The server is, well, has to be a 2012 or later server, but the client side, the bit you install on the test machine, *should* be capable of supporting any previous version of windows 10. This is what the docs say, this is what I was told on the driver forum group. But when I tried it...
'get stuffed, your not having that'
My gripe is that there are more versions to get your head around. Have you seen the help on the net to do various things? Each version has its own GUI, its own way of doing it. It is getting silly. In five years we will have 20 versions of windows 10!
This is what the docs say, this is what I was told on the driver forum group. But when I tried it...
'get stuffed, your not having that'
So then that's a bug (it's supposed to work) and somebody needs to fix it.
I think sticking to the lowest common denominator (the oldest version of Windows 10 still supported) is viable for now, unless you're really on the cutting edge and using things that only exist on the later builds. I'm not seeing any compelling feature that I must integrate with my apps.
That brings it down to a single OS target, despite the build sprawl. I treat all those builds as one and the same, and so far it's been working out just fine for me. Obviously YMMV.