PHPStorm updated from 2020.2.4 to 2021.2.2 - no new folder created, old icon remains

At the outset, it looks cosmetic. However, thinking if something fundamental is broken.

Can you help resolve this? Or confirm if this is normal and not of concern?

5 comments
Comment actions Permalink

Hi there,

How did you update?

  • If it was a patch / run from within the IDE then yes, it uses the same folder when current version is installed (in-place upgrade).
  • Standalone installer (which I personally use and recommend) always uses a new folder (you have to manually download and install using full installer). Can add desktop icon.
  • JetBrains Toolbox App will install each version into separate folder and that will be a separate location (not Program Files)

None of these will update pinned Task Bar icon/description (i.e. I've installed 2021.2 and pinned to a Task Bar; since then I have installed 2021.2.1 and 2021.2.2 yesterday; the Task Bar icon still shows "2021.2" text on hover).

2
Comment actions Permalink

Thanks for your detailed response Andriy Bazanov.

It was from within the IDE. While taking the SS also realized that there was no separate folder for 2020.2.4 too. So assuming that this is not a problem, correct?

Curious on why you use the Standalone installer despite Jetbrains (JB) recommending the toolbox? Had attempted to use the toolbox earlier, but their FAQ suggests to uninstall all apps before proceeding - making it cumbersome and potentially error-prone for new users. 

Thanks!

0
Comment actions Permalink

Curious on why you use the Standalone installer despite Jetbrains (JB) recommending the toolbox?

Because

  1. I do not like in-place upgrade -- it's messy as it sometimes does not update all files (e.g. due to antivirus... or (rare) issues in the patch itself)
  2. When installer uninstalles previous version, I'm choosing "remove caches and indexes". Sure, I'm loosing stuff like Local History but in return I do not have issues with updated stubs (old PhpStorm versions often had issues with them... and I had to use Invalidate Caches anyway)
  3. I have PhpStorm only -- no benefits in Toolbox App for me. Plus, why do I need to spend extra 300-500MB or RAM just for "launcher".
  4. Toolbox App installs every new version in a separate folder .. and it's not in Program Files.
  5. I can manually manage having both stable + EAP versions of PhpStorm via installers. I just see zero benefits for me.
2
Comment actions Permalink

Given that I myself use PhpStorm only, does not make sense to let another 300-500MB RAM be consumed by the launcher.

Regarding the in-place upgrade - how do you handle backing up keymaps, live templates, and other customizations? Because, if a new upgrade changes the underlying format of files storing these customizations then they would be lost, isn't it? Or does the Settings Sync feature takes care of this?

0
Comment actions Permalink

Regarding the in-place upgrade - how do you handle backing up keymaps, live templates, and other customizations? Because, if a new upgrade changes the underlying format of files storing these customizations then they would be lost, isn't it?

Why should be they lost? The IDE settings are stored separately; each version has own folder. https://www.jetbrains.com/help/phpstorm/directories-used-by-the-ide-to-store-settings-caches-plugins-and-logs.html#config-directory

I've been using PhpStorm from v0.6 or so (before v1 was even released). Have used every single version and had no issues with settings after installing a new version. If there were issues then they were affecting other users as well; nothing individual that is specific to me.

Even if a new version changes config storage (e.g. certain settings before were stored all in one file and now each subsystem has own separate config file) the old settings for old version remains intact. Plus... you do (at least weekly) backups of your PC (at least of a system disk), right?

1

Please sign in to leave a comment.