Hi karl, Do post back and let us know if copying the Application directory works. Like PhistucK asked, has that method actually been tried? I re-tested this earlier and it seemed to have problems. The copied Chrome didn't seem to start at all.
I recall previous information from a long time that Chrome/Chromium does work from its own directory. Possibly that information refers only to the Snapshots or Continuous Chromium ZIPped builds that can be unzipped? Maybe that does not apply to official Google Chrome installs.... :-( If copying the Application directory fails, I guess your next simplest workaround is to create 2 login accounts on your Windows computer. Since Chrome is installed per-user into his own Local Settings \Application Data directory, you can install Beta for one account and Dev for the other. Then you just have to logout and re-login to test different official Chromes. Also, this method will allow the update check to work properly. On Dec 17, 12:41 pm, karl <k...@interclue.com> wrote: > Thanks all. > > I think I'll go for the (normal) install and then coping the Chrome > \Application directory then use set --user-data-dir for the separate > profile. > > I'll have to think of some way to get the updates to work though, > because there's no point in testing against obsolete versions of chrome -- 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.
