This question has come up several times... how to get Gears to work with an embedded instance of the WebBrowser control. http://groups.google.com/group/gears-eng/browse_thread/thread/f22ce1f101cc4c01/6743bee0dd9aebdf?lnk=gst&q=Ramesh#6743bee0dd9aebdf
The Gears.BHO is not being loaded and initialized. The BHO is what kicks Gears into configuring its network intercept hackery. Many applications embed browser controls and we don't want to load Gears into them indiscriminently. As an app developer, you should be able to explicitly load and initialize the Gears.BHO in your application. When creating your embedded browser control, you will want to... * create an instance of the Gears.BHO COM object (it is registered in the registry) * get a reference to it's IObjectWithSite interface pointer * call the SetSite(iunknownOfEmbeddedBrowserControl) Caveats... should work, havent' tried it myself, we certainly don't test it in this fashion. Hope this helps. Michael 2008/9/25 NealLee <[EMAIL PROTECTED]> > > > Kurabi, can you specify that small minor bug? > I encounter the problem as TatvaSoft meet, I use the .net webbrowser > control, but it seems can't access local cached files, so I can't > display the page when I offline. > > On 9月5日, 下午3時10分, M.Kurabi <[EMAIL PROTECTED]> wrote: > > TatvaSoft, I am currently working on a project that uses gears in a > client > > side application. The browser control I am using is an ATL library brower > > control. Everything works fine except for one small minor bug. > > > > On Thu, Sep 4, 2008 at 1:30 PM, Aaron Boodman <[EMAIL PROTECTED]> wrote: > > > > > Gears isn't designed to be used in client-side applications. It would > > > probably require significant changes in Gears in order to work well. > > > > > - a >
