Easy, There are two things you can do. 1. create another user profile in Windows. Chrome is installed in the user profile instead of the Program Files, so each user account on the machine can carry it's own separate installation of Chrome.
2. Use Chromium as the dev build and Chrome as the beta on the same profile. Chromium is the open source backbone of Chrome and you can download nightly builds of Chromium which do not auto update and are identical to Chrome except for the Google branding. Chromium builds, being nightly, are usually ahead of the dev channel, but since they don't auto-update, you can choose the build that corresponds with the current Chrome dev build or just use the bleeding edge builds. On Dec 16, 5:46 pm, karl <k...@interclue.com> wrote: > I'm developing Lazarus:Form Recovery for chrome and find I need to > test it on the beta channel of chrome as well as develop on the dev > channel. At the moment I'm having to resort to running the beta > version in a Virtual Machine and using the dev verion to develop on. > > In my ideal world I would be able to: > * Have separate chrome executables for dev, beta, and stable builds of > chrome. > * Have one or more separate profiles for each of the executables > (profiles should not be shared between channels) > * Each channel should update normally via the google update exe, so > that I keep the latest version of each. > > Does anyone know of a way where I can have separate instances of > chrome (with different profiles for each) running on the same machine, > preferably without having to jump through the Virtual Machine route. > > note: OS is WindowsXP and or Windows 7 > > Cheers -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
