Question for developers: Do you have a policy, preference, or SOP for dealing with file versioning, date and time stamps, etc.? I see some products where the executable and support files (typically DLLs) all share the same date and time stamp. Sometimes the date and time seem to correlate to the executable version in some fashion; sometimes there's no obvious association.
SCBWV 441 Junior Poster
Recommended Answers
Jump to Post— Salem 6,025It's a dumb trick which tells you nothing useful.
One file copy later, and there's a chance the information is gone for good.
Some archiving / backup programs also like to monkey around with file dates as well.
All 2 Replies
rproffitt 3,266 https://5calls.org Team Colleague
This varies with each company. Sometimes it's done on purpose. Ask why are all Windows drivers dated June 21, 2006?
There is no industry standard here. But I will share that when I did such work I accepted whatever SOP the company wanted.
Salem 6,025 Posting Sage
It's a dumb trick which tells you nothing useful.
One file copy later, and there's a chance the information is gone for good.
Some archiving / backup programs also like to monkey around with file dates as well.
rproffitt commented: 🙊🙉🙈 +17
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.