[SERVER-3993] Windows executables should include a Version resource Created: 01/Oct/11  Updated: 19/Nov/16  Resolved: 03/Nov/16

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: 2.0.0
Fix Version/s: 3.4.0-rc3

Type: Bug Priority: Minor - P4
Reporter: Tad Marshall Assignee: Mark Benvenuto
Resolution: Done Votes: 2
Labels: Windows, build-planning, community-team, platforms-hocr
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows


Issue Links:
Duplicate
is duplicated by SERVER-27095 Windows executables should include ve... Closed
is duplicated by SERVER-16098 MongoXXX binaries on windows missing ... Closed
Related
is related to SERVER-26393 Bin folder files do not get replaced ... Closed
Backwards Compatibility: Fully Compatible
Operating System: Windows
Sprint: Platforms 2016-10-31, Platforms 2016-11-21
Participants:

 Description   

Windows executables can include a version resource that provides a version number and other information. Some of this information can be viewed in Windows Explorer when viewing the Properties of a file; in Windows 7, the Details tab shows this information when it is present. The main reason why version resources are helpful is that they make it possible to see the version information without running the program. A --version switch is a fine thing, but it is not a substitute for data that can be scanned by inventory programs that scan a computer to collect information on what is installed. None of the MongoDB programs for Windows include any version resources.
Note to implementer: Visual Studio can create RC files and allows some of the possible data to be added using the GUI, but it has a bad habit of removing information that it doesn't recognize. The best approach is usually to create a version resource in MSVC and then move that section to another file and modify the .RC file to include your other file. This way, Visual Studio won't remove anything that you add that it doesn't understand.



 Comments   
Comment by Githook User [ 03/Nov/16 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-3993 Windows File Version stamping
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/7474ecd3a4b053ee14722c3e6f708c64f8ca9d5a

Comment by Githook User [ 03/Nov/16 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-3993 Windows File Version stamping
Branch: master
https://github.com/mongodb/mongo/commit/724ce700122d28ddadf9f4403e82e87e722a7838

Comment by Githook User [ 03/Nov/16 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-3993 Windows File Version stamping
Branch: master
https://github.com/mongodb/mongo/commit/27de9170811de2454a0b59c234fd9661d3a85c2f

Comment by Brian Samek [ 17/Oct/16 ]

chrismielca suggested in SERVER-26393 that

I would also suggest that the installer verifies if another version is installed on the OS, asks the user whether to replace or create a new one (reflect changes in "Programs & Features" if it is replaced). When the user selects the installation location, it should notify that an instance is installed in that location (or sub-location), if that's the case.

Generated at Thu Feb 08 03:04:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.