Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Atom release channels can't be installed side-by-side on Windows #9247

Closed
MethodGrab opened this issue Oct 21, 2015 · 17 comments

Comments

Projects
None yet
@MethodGrab
Copy link

commented Oct 21, 2015

Expected
According to the beta info page Atom Beta should "run side-by-side with Atom stable". To me that reads like I should be able to have both the beta and stable installed (and even running) simultaneously on the same system (like with Chrome's stable & beta releases) and there should be separate links to run each build.

Actual
On Windows (7 x64), when I install the beta (1.1.0-beta1), it replaces the context menu "Open with Atom" shortcut and the start menu shortcuts with the beta so there is no apparent way to run stable without reinstalling.
Reinstalling stable works but it replaces all the shortcuts with links to the stable version so there is no way to run the beta without re-installing.

image

@mnquintana

This comment has been minimized.

Copy link
Member

commented Oct 21, 2015

@benogle

This comment has been minimized.

Copy link
Contributor

commented Oct 21, 2015

@maxbrunsfeld

This comment has been minimized.

Copy link
Contributor

commented Oct 23, 2015

Ok, I had to stop work on this for the time being because of some PathLength issues on windows. We need to upgrade our build infrastructure to use npm 3, which does a better job of reducing path nesting. Until that time, I'm leaving this open.

@damieng

This comment has been minimized.

Copy link
Contributor

commented Feb 26, 2016

With the file associations and shell integration having the beta executable named something different - atombeta.exe for example - would also make this work better. Thoughts?

@maxbrunsfeld

This comment has been minimized.

Copy link
Contributor

commented Feb 26, 2016

having the beta executable named something different - atombeta.exe for example - would also make this work better.

👍 Ah, I didn't realize that. We already rename a bunch of stuff based on the channel (stable vs beta) in the build scripts, so this would just be one more.

@lee-dohm lee-dohm changed the title Atom Beta Side by Side Atom Beta isn't Side by Side on Windows Apr 24, 2016

@damieng

This comment has been minimized.

Copy link
Contributor

commented May 5, 2016

Now the shell integration is coming out of the installer and into Atom settings we should make sure we use productName instead of atom.exe everywhere when we do that work in #5901

@damieng

This comment has been minimized.

Copy link
Contributor

commented Jul 20, 2016

Included in the forthcoming shell integration options.

@damieng damieng closed this Jul 20, 2016

@calebmeyer

This comment has been minimized.

Copy link

commented Jul 22, 2016

@damieng what's the process/timeline for getting both installed side by side on windows?

@damieng

This comment has been minimized.

Copy link
Contributor

commented Jul 23, 2016

It's checked into master now on both atom/atom and atom/settings-view and should ship in Atom 1.10.

@Ben3eeE

This comment has been minimized.

Copy link
Member

commented Oct 26, 2016

Reopening because I am not able to install Atom beta side by side with Atom stable on Windows 7. Installing beta removes the stable install. See below for a full list of what I did to try and install Atom 1.12.0-beta4 side by side with Atom 1.11.2.

I can test it out on Windows 10 later if required to see if stable and beta side by side works there.

Originally reported in: #13016 so not alone seeing this.

Windows 7 - Trying to install stable and beta side by side.

  1. Uninstalled Atom 1.12-beta4 using Programs and Features found in the Control panel.
  2. Removed the .atom folder from %USERPROFILE%.
  3. Removed the atom folder from %localappdata%. It contained update.exe and .dead.
  4. Expected: Atom to be uninstalled. Actual: Atom pin is still on the taskbar, clicking it gives an error that it might have been moved, renamed or deleted asking me to remove the pin.
  5. Unpinned Atom from the taskbar by clicking Yes on the dialog.
  6. Installed Atom 1.11.2 using AtomSetup.exe downloaded from atom.io.
  7. Expected and Actual: Atom 1.11.2 starts after install, all settings lost.
  8. Answered yes on the telemetry consent and unchecked the Show On Start option for the welcome guide.
  9. Opened the settings-view using Ctrl+,
  10. Navigated to the System tab and checked all three options.
  11. Pinned Atom to the taskbar.
  12. Closed Atom 1.11.2.
  13. Checked %localappdata\atom it contains the app-1.11.2 folder.
  14. Installed Atom 1.12.0-beta4 using AtomSetup.exe downloaded from atom.io.
    1. Atom 1.12.0-beta4 starts.
    2. Atom does not ask for telemetry consent or show the welcome guide.
    3. Atom 1.11.2 is not in %localappdata%\atom. Only app-1.12.0-beta4.
    4. Atom is still pinned to the taskbar and can open from there but it has the icon from stable.
    5. Open with Atom context menu works, icon from beta and opens Atom 1.12.0-beta4.
  15. Checked the Systems tab all three options are checked.

@Ben3eeE Ben3eeE reopened this Oct 26, 2016

@damieng

This comment has been minimized.

Copy link
Contributor

commented Oct 26, 2016

Atom Beta is expected to use the same config and settings as regular Atom right now so I wouldn't expect it to show the welcome guide or telemetry consent.

The real problem right now is that beta and non-beta on Windows share the same setup-id in Squirrel so one is considered an upgrade to the other.

One option for now would be to use the beta zip and unpack that somewhere. That should allow you to run side-by-side. If you want the beta to also use a separate config then you should be able to create an empty .atom folder in the folder about where you unpacked the beta, e.g.

c:\apps\atombeta
c:\apps\.atom
@jerone

This comment has been minimized.

Copy link

commented Nov 19, 2016

I see exactly the same happening as @Ben3eeE is describing. While installing any version of Atom (stable, beta or dev) the previous Atom installation is being removed from %LOCALAPPDATA%\atom\.

Windows 7 EN 64-bits

@vvs

This comment has been minimized.

Copy link

commented May 31, 2017

Just installed Atom 1.18 beta (Windows 10, x64) and it has deleted the stable Atom version (1.17). If the issue is not going to be fixed, it would be good to remove the wrong message on the Atom beta page that the beta can be used side-by-side.

@sonokamome

This comment has been minimized.

Copy link

commented May 31, 2017

Heya Vlad, no it works in other platforms as far as the side-by-side install. It's just in Windows where this is currently an issue. side-by-side installs work fine in UNIX and UNIX-like environments. They're still working on it. In the meantime, refer to @damieng 's suggestion:

Atom Beta is expected to use the same config and settings as regular Atom right now so I wouldn't expect it to show the welcome guide or telemetry consent.

The real problem right now is that beta and non-beta on Windows share the same setup-id in Squirrel so one is considered an upgrade to the other.

One option for now would be to use the beta zip and unpack that somewhere. That should allow you to run side-by-side. If you want the beta to also use a separate config then you should be able to create an empty .atom folder in the folder about where you unpacked the beta, e.g.

c:\apps\atombeta
c:\apps\.atom

@anaisbetts

This comment has been minimized.

Copy link
Contributor

commented Jun 14, 2017

Hi all, I've written the first version of a tool designed to solve this problem: https://github.com/atom/avm

Here's how to get started:

npm install -g atom-version-manager

## Install the stable version:
avm switch stable

## Switch to the beta
avm switch beta

The initial run of these commands will take awhile as it downloads Atom and installs it, but from then on switching between the two will be very fast (i.e. 2-3 sec or so). Let me know if this helps!

@MartyGentillon

This comment has been minimized.

Copy link

commented Jun 18, 2017

At a minimum, it would be nice to mention something about this on the atom beta website. It's really annoying to discover after the fact that it blew away my stable atom install.

@MorganMarshall

This comment has been minimized.

Copy link

commented Aug 15, 2017

Guys, tons of people are wasting a lot of time on this. Like everyone is suggesting please remove the side by side sales pitch from the site, at least on windows side. From the looks of this thread it hasn't worked in years. Its causing a lot of confusion and cursing.

@daviwil daviwil referenced this issue Jun 19, 2018

Merged

Implement RFC 002: Atom Nightly Releases #17538

12 of 12 tasks complete

@daviwil daviwil changed the title Atom Beta isn't Side by Side on Windows Multiple Atom release channels can't be installed side-by-side on Windows Jul 24, 2018

@Ben3eeE Ben3eeE added triaged and removed bug labels Sep 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.