You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GNS 3 needs to start doing inline updates. Making us download a new file and re-install every time there is a newer version is getting old. It seems the VM is capable of this however the desktop software has not gotten to this level.
The text was updated successfully, but these errors were encountered:
I am completely against "forced" inline updates.
IMHO, inline updates are too massively complicated for the gns3 developers and are error prone.
On Windows 10, I can upgrade to a new version of GNS3 (with the GNS3 VM) and rollback within 15 minutes flat of detecting a failure in the new version of GNS3 - and I lose no projects. I will always succeed and never fail - if I follow my rules.
On Windows 10, I start with a working gns3 and a working gns3 vm and a working gns3 configuration - I protect them and block windows updates (for 7 days or so) and install no new software; I can rollback and I will never fail.
In my own little world, I would probably force all gns3 projects that were created in, i.e. gns3 version 2.2.39 and loaded in gns3 version 2.2.40, be forcibly saved into ~/GNS3/projects/2.2.40
That being said, backing up my windows gns3 profiles with powershell for default, Vm (vmware workstation), Pl (vmware player), and Re (remote server) was not fun to implement :(
GNS 3 needs to start doing inline updates. Making us download a new file and re-install every time there is a newer version is getting old. It seems the VM is capable of this however the desktop software has not gotten to this level.
The text was updated successfully, but these errors were encountered: