Go Back   Winamp & Shoutcast Forums > Developer Center > NSIS Discussion

View Poll Results: How should Windows 10 releases be identified?
16299 | The build number 15 55.56%
1709 | The release date 10 37.04%
FallCreatorsUpdate | The semi-public name 1 3.70%
Redstone3 | The internal code name 0 0%
Something else? 0 0%
I don't care about Windows 10 releases 1 3.70%
Voters: 27. You may not vote on this poll

 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old 15th April 2018, 22:02   #1
Anders
Moderator
 
Anders's Avatar
 
Join Date: Jun 2002
Location: ${NSISDIR}
Posts: 4,976
WinVer Windows 10 release identification

I'm considering adding more detailed Windows 10 detection support to WinVer and I'd like to get some feedback on the API design. How should each release be identified?

Technical note: Anything other than the build number will most likely require a lookup at compile-time and therefore a new NSIS release will be required to support new Windows 10 releases. If we choose something other than the build number, a macro for the build number will still be available.

IntOp $PostCount $PostCount + 1
Anders is offline   Reply With Quote
 
Go Back   Winamp & Shoutcast Forums > Developer Center > NSIS Discussion

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump