View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008520 | MMW v4 | Other | public | 2011-10-14 16:51 | 2011-10-25 14:47 |
| Reporter | lowlander | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | reopened | ||
| Product Version | 4.0 | ||||
| Summary | 0008520: Portable install doesn't remember last portable install folder | ||||
| Description | MediaMonkey 3 is installed (custom folder) and MediaMonkey 4 (1444) was installed as Portable Install (custom folder). Upon upgrading to 1445 MediaMonkey defaulted to the MediaMonkey 3 install folder. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Isn't this actually an intended affect of portable installs? I leaves no traces (other than the install folder) on the computer. How would it remember the install directory for portable install without saving this information in the registry or something? |
|
|
Yes, this is indended affect. MediaMonkey cannot remember last installed Portable folder, because when installing in Portable mode then _everything_ is installed just to the portable folder (that can be on an external and unplugged device). |
|
|
I think the process still isn't perfect though I understand that it can't find the existing portable install. - It shouldn't offer to install the portable install an existing normal install, I guess best is to start in My Computer and let user decide which folder to install in - When upgrading and selecting the existing portable install folder it still appends MediaMonkey as folder. It should recognize it should be in selected folder. - When installing in the Portable folder it asks to overwrite files, but didn't ask that when installing in the normal 3.x install folder. - As the installer can't locate the existing Portable installation MediaMonkey could really use an in application upgrade process that will automatically update the existing install. |
