Rank: Advanced Member
Groups: Member
Joined: 1/5/2015
Posts: 60
|
Hi I've recently been experimenting with your multi-dll build for the WebBrowser to save on memory usage, but I've encountered a problem with caching. I use the most recent multi-dll build http://apps.essentialobjects.com/files/builds/EO.WebBrowser.MultiDLLs.2014.0.35.zipCaching is enabled by setting "CachePath" on the "Runtime" object as your documentation advise, and it works when I use dlls from the single build. It seems that none of the Runtime options works, as "RemoteDebugPort" also has no effect when using the multiple dlls. Thanks
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
We have tested this and it works fine during our test. For example, we used the following steps to test RemoteDebugPort:
1. Download and install EO.Total package. This will install the single DLL build;
2. Download the multi-DLL build. Unzip all the files, then copy EO.WebBrowser.dll and EO.WebBrowser.Wpf.dll into "Program Files (x86)\Essential Objects\EO.Total 2014". This overwrites the original single DLL version of these two DLLs;
3. Load and build the TabbedBrowser sample (using Debug configuration);
4. Copy all other DLLs in the multi-DLL download into bin/Debug directory of the TabbedBrowser sample project;
5. Run TabbedBrowser sample. This now uses the multi-DLL build;
6. Type "http://localhost:1234" in the address window, you should see the remote debug landing page. TabbedBrowser sample sets RemoteDebugPort to 1234 in App.xaml.cs/App.xaml.vb;
Please try the same steps and let us know if it works for you.
Thanks!
|
Rank: Advanced Member
Groups: Member
Joined: 1/5/2015
Posts: 60
|
I've tried your approach and it works for me as well, both remote debugging and caching works in the sample with multi-dlls :)
I must be doing something wrong in my own application.
Thanks
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
No problem. Please feel free to let us know if there is anything else.
Thanks!
|