I am developing a specific server. Until now, two versions could not be installed at the same time. We are changing this now, and the question arose: should the version number be added to the server components or not? The server contains 3 exes and 5 dlls (some COM, some native VC ++). Should any or all of the names have a version (Serv71.exe, module71.dll) or not?
From a professional point of view, this should facilitate server management. If a particular case erroneously works, it will be identified in the task manager. In addition, there is no chance that a poor installation will end up having versions of mixed components without noticing them.
On the opposite side, this would make development a little more difficult. The server is not a standalone product, but rather part of our application infrastructure. This means that he receives the main version of the application. In this case, a specific component will need to get a different name, even if it has not changed between versions.
In general, this is not a very important issue. Perhaps we can get along in both directions. Having said that, I may have missed the argument of the winner in favor of one of the strategies. What is the general choice? what are you doing?
Edit: I am familiar with COM and file metadata version control versions and agree that file version control is redundant. I am trying to figure out what is more important - a constant excess overhead service or a rare gain in service.