Suggestion: Have the self-extracting archive's default extract path include a sub-folder?
Posted: 2017-09-01, 06:10
Would it not make more sense for the default extraction path for the self-extracting archive's include a sub-folder?
Currently, if the self-extracting archive is located in "D:\programs" and you run it, the default extraction path would be "D:\programs\", which then results in the EXE being located at "D:\programs\palemoon-portable.exe". Would it not instead make more sense if the default extraction path said something along the lines of "D:\programs\palemoon-portable\", which would then result in the EXE being located at "D:\programs\palemoon-portable\palemoon-portable.exe"? And since this would just be the default path, the user could easily still change the extraction path to "D:\programs\" which would then result in the EXE being located at "D:\programs\palemoon-portable.exe".
This came to mind because I had to update my .NET framework yesterday, and its initial extraction of the installation files works exactly like my suggestion, and I know that the initial extraction for the Radeon GPU drivers installer as well as any and all PortableApps extractors/"installers" all behave in the same way as my suggestion.
Currently, if the self-extracting archive is located in "D:\programs" and you run it, the default extraction path would be "D:\programs\", which then results in the EXE being located at "D:\programs\palemoon-portable.exe". Would it not instead make more sense if the default extraction path said something along the lines of "D:\programs\palemoon-portable\", which would then result in the EXE being located at "D:\programs\palemoon-portable\palemoon-portable.exe"? And since this would just be the default path, the user could easily still change the extraction path to "D:\programs\" which would then result in the EXE being located at "D:\programs\palemoon-portable.exe".
This came to mind because I had to update my .NET framework yesterday, and its initial extraction of the installation files works exactly like my suggestion, and I know that the initial extraction for the Radeon GPU drivers installer as well as any and all PortableApps extractors/"installers" all behave in the same way as my suggestion.