Enable side-by-side beta and dev channels.

chrome/install_static/google_chrome_install_modes.cc

Index: chrome/install_static/google_chrome_install_modes.cc
diff --git a/chrome/install_static/google_chrome_install_modes.cc b/chrome/install_static/google_chrome_install_modes.cc
index 4202e85bd6adf968961b0b7176d029076c9ad9a2..53ffdd179c840f81f9c566cd071cf04258417cc3 100644
--- a/chrome/install_static/google_chrome_install_modes.cc
+++ b/chrome/install_static/google_chrome_install_modes.cc
@@ -47,6 +47,52 @@ const InstallConstants kInstallModes[] = {
         icon_resources::kApplicationIndex,  // App icon resource index.
         IDR_MAINFRAME,                      // App icon resource id.
     },
+    // A secondary install mode for Google Chrome Beta
+    {
+        sizeof(kInstallModes[0]),
+        BETA_INDEX,     // The mode for the side-by-side beta channel.
+        "chrome-beta",  // Install switch.
+        L" Beta",       // Install suffix.
+        L"Beta",        // Logo suffix.
+        L"{8237E44A-0054-442C-B6B6-EA0509993955}",  // A distinct app GUID.
+        L"Google Chrome Beta",                      // A distinct base_app_name.

[robertshield, 2017/04/06 14:31:02]

To make sure I understand how running side-by-side works: 

* this distinct base_app_name is used to create a different default
user_data_dir
* the different default user_data_dir is used by the process singleton to enable
different versions of the browser to run at the same time

Are there combinations of environment state where this will break down (thinking
registry policy or environment variable)? Reading
https://codesearch.chromium.org/chromium/src/chrome/install_static/user_data_...
it looks like there might be, but that state doesn't look like something a user
would get into accidentally.

[grt (UTC plus 2), 2017/04/20 13:53:04]

The install_suffix is used for that. The base_app_name is for registering as a
browser with Windows.
This is correct.
I don't think so. The install mode is sniffed from the path of chrome.exe in
GetInstallSuffix
(https://codesearch.chromium.org/chromium/src/chrome/install_static/product_in...).
If chrome.exe is in ...\Chrome Beta\Application, then this mode is picked.
Following that, the default user data dir will be in ...\Chrome Beta\User Data.
The only breakdown would be someone running Beta (for example) and then using
--user-data-dir= to pick a parallel install's dir. You get what you ask for in
that case. :-)

Is there something else you see/are thinking of that I'm missing?

[robertshield, 2017/04/21 03:10:11]

Will e.g. beta and dev SxS installs pick up the same values from
https://www.chromium.org/administrators/policy-list-3#UserDataDir ? If so, would
having that policy set make having SxS installs present behave strangely / not
work due to profile incompatibility?

+        L"ChromeBeta",                              // A distinct base_app_id.
+        L"ChromeBHTML",                             // ProgID prefix.
+        L"Chrome Beta HTML Document",               // ProgID description.
+        L"{8237E44A-0054-442C-B6B6-EA0509993955}",  // Active Setup GUID.
+        L"",                                        // CommandExecuteImpl CLSID.
+        L"beta",                                    // Forced channel name.
+        ChannelStrategy::FIXED,
+        true,   // Supports system-level installs.
+        false,  // Does not support in-product set as default browser UX.
+        true,   // Supports retention experiments.
+        false,  // Did not support multi-install.
+        icon_resources::kBetaApplicationIndex,  // App icon resource index.
+        IDR_X005_BETA,                          // App icon resource id.
+    },
+    // A secondary install mode for Google Chrome Dev
+    {
+        sizeof(kInstallModes[0]),
+        DEV_INDEX,     // The mode for the side-by-side dev channel.
+        "chrome-dev",  // Install switch.
+        L" Dev",       // Install suffix.
+        L"Dev",        // Logo suffix.
+        L"{401C381F-E0DE-4B85-8BD8-3F3F14FBDA57}",  // A distinct app GUID.
+        L"Google Chrome Dev",                       // A distinct base_app_name.
+        L"ChromeDev",                               // A distinct base_app_id.
+        L"ChromeDHTML",                             // ProgID prefix.
+        L"Chrome Dev HTML Document",                // ProgID description.
+        L"{401C381F-E0DE-4B85-8BD8-3F3F14FBDA57}",  // Active Setup GUID.
+        L"",                                        // CommandExecuteImpl CLSID.
+        L"dev",                                     // Forced channel name.
+        ChannelStrategy::FIXED,
+        true,   // Supports system-level installs.
+        false,  // Does not support in-product set as default browser UX.
+        true,   // Supports retention experiments.
+        false,  // Did not support multi-install.
+        icon_resources::kDevApplicationIndex,  // App icon resource index.
+        IDR_X004_DEV,                          // App icon resource id.
+    },
     // A secondary install mode for Google Chrome SxS (canary).
     {
         sizeof(kInstallModes[0]),