3 ms·
The preferred way is App Paths [1], it's just that there's not really a good UI for that and most people are used to Unix-style PATH environment variables so a
by WorldMaker 11y ago
The preferred way is App Paths [1], it's just that there's not really a good UI for that and most people are used to Unix-style PATH environment variables so a lot of software depends on that that maybe doesn't actually need to and a lot of installers are built for that because the person building the installer didn't find the App Path tools but did find the Environment Variable smasher.
[1] http://blogs.msdn.com/b/oldnewthing/archive/2011/07/25/10189298.aspx http://blogs.msdn.com/b/oldnewthing/archive/2011/07/25/10189...
- WorldMaker 11y agoAlso the fact that for compatibility reasons the CMD shell doesn't do App Path-based lookups, but in some ways that is an implementation detail (and what "start.exe" and its PS equivalent are for), and something that only really impacts shell-using developers.