ns-verrsrc-vs_fixedfileinfo.md: dwFileDateMS/dwFileDateLS #1553
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@skissane : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
Change sent to author
desktop/prod
sdk-api-reference/tech
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In practice,
dwFileDateMSanddwFileDateLSare almost never used and are expected to be zero.From what I can gather, Microsoft's own build tools have never set them to a non-zero value, going back to Windows 3.x. It appears very few third party tools do so either. While executables having non-zero values for this field reputedly exist, nobody seems to be able to produce an example of one.
And yet, the documentation doesn't mention this significant fact–I think it should.