Chris Angelico <rosuav at gmail.com> wrote: >> BUT -- Steve Dower seems to have identified that the wonders of dll hell >> never cease, and this isn't possible anyway. Oh well. > > I'm not entirely grasping what's happening here. There are multiple > versions of msvcp140.dll floating around out there; what happens if > one app requires one of them and another requires another? Can you > simply say "take the newer one"? Is there a way to instantly recognize > that there's a newer one available, and ignore the older one? > Versioning is a *pain*. Windows executables can and should ask for specific versions of the DLLs in the manifest (an XML file embedded in the EXE). Details here: https://en.wikipedia.org/wiki/Side-by-side_assembly Sebastian
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4