4 ms·
Is application dependency management in windows normally a problem? Apart from the odd runtime, I expect Windows applications to be pretty much self contained,
by alkonaut 12y ago
Is application dependency management in windows normally a problem? Apart from the odd runtime, I expect Windows applications to be pretty much self contained, and not dependent on any system-wide libraries (which is a huge benefit I think).
For development it's a different story, there you can have several levels of dependencies, but there NuGet at least appears at least as powerful as similar options on other platforms.
- SwellJoe 12y ago"but there NuGet at least appears at least as powerful as similar options on other platforms" That seems unlikely (i.e. can we upgrade the whole OS with NuGet?), but it does look like it is, at least, aware of some of the problems an actual package manager solves.
- alkonaut 12y agoNot sure if I was unclear, I was referring to NuGet package management for development, comparing it to e.g. similar systems such as npm.
- SwellJoe 12y agoNo, I understood. It seems like NuGet is an acceptable substitute for npm...but neither is an acceptable substitute for apt or yum (whether for development or whatever).
- ioddly 12y ago> Is application dependency management in windows normally a problem? It has its own name. http://en.wikipedia.org/wiki/DLL_Hell http://en.wikipedia.org/wiki/DLL_Hell
- mdlowman 12y agoDLL hell certainly used to be a big issue in Windows. But I disagree that it remains a major factor; Windows apps are increasingly bundled and Windows system functions that used to be the cause of these issues, like DirectX, are packaged as redistributables that allow side-by-side installs.
- ekianjo 12y ago> like DirectX, are packaged as redistributables that allow side-by-side installs. No wonder everything gets so messy in the registry :)
- PeterLindt14 12y agoExactly, thank you.
- thrownaway122 12y agoHow do they handle security updates? Does every app have to update all its own libraries in an e.g. heartbleed scenario?
- useerup 12y agoThere's the WinSxS and the GAC (Global Assembly Cache). In SxS actually means side-by-side. Both WinSxS and the GAC supports multiple versions of the same libraries, and the program manifests set up policies for which library versions they require/accept. An application may for instance say that it accepts any newer "minor" version. For security patching you can replace a library with a new "build". So if an application uses libraries placed in WinSxS or the GAC it will pick up any centrally patched libraries without the risk of jumping to a too new version with breaking changes. The new version can exist alongside older versions and they can all be patched - for security reasons or otherwise. A vendor can also distribute libraries alongside the application - in the application library itself. In that case the responsibility for patching is placed squarely on the vendor of that application.
- alkonaut 12y agoNot sure who "they" is here, ut in windows: pretty much, yes. You can't have it both ways. So you either have a centralized/shared lib environment where you may run into conflicts but you get centralized patching, or you have self contained applications where you need to patch each one but you never have lib dependency/upgrade issues. Simple as that.
- tomc1985 12y agoJust want to note that Windows has a whole mess of dependency-management, much of it provided by the service that handles those MSI installer files.