Hi,
this issue is similar to this one, a difference is whether iTwin Synchronizer or iModelBridge is updated.
Problem: When iTwin Synchronizer is upgraded (e.g. as now from 1.0.132 to 1.0.140, folder C:\Users\<user>\AppData\Local\iTwinSynchronizer\is not cleaned, so both app-1.0.132 and app-1.0.140 folders exist in parallel.
C:\Users\<user>\AppData\Local\iTwinSynchronizer\
It represents about 700MB disk space lost, and because the installation is upgraded quite often (and I appreciate fast development and release ;-), disk space wasting grows step by step.
Any plans to make iTwin Synchronizer (and iModelBridges also) installation more cautious about the space and obsolete files and folders?
With regards,
Jan
The auto-update mechanism should only ever keep 1 old copy of the application around... are you seeing it build up more than 1 backup? I believe thephilosophy behind the standard library we use is to keep 1 version as a failsafe for a catastrophic update.
Hi Jeff,
thanks for your explanation. I think I saw more versions in the past, now it seems to be as you wrote: current and one older versions (folders) exist.
Even when I agree with the idea to have the backup, I guess after the first successful start of the updated version, the backup should be removed also. Even when disk space is quite cheap today, 0.6 GB is not small amount, especially when Synchronizer location is fixed at system drive in user profile.
BTW I do not see the same behavior when i-model Bridges are updated. I will update this discussion.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point