|
Rank: Newbie Groups: Member
Joined: 3/23/2015 Posts: 8
|
I have been using EO Webbrowser 2014 for .NET win forms. Now I try to update to 2015 version and I cannot use the controls. I add the reference to EO.WebBrowser add the items in toolbox then when I try to drag the WebView or WebControl item into a windows form I get an error. Any ideas? http://www.essentialobjects.com/Products/WebBrowser/WinForm.aspxThis cannot be correct as the dll named is tiny. Seems there is lacking a simple descrtiption of what dlls you need to include in your project.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,229
|
Hi,
EO.WebBrowser 2015 splits code into three DLLs: EO.Base.dll, EO.WebEngine.dll and EO.WebBrowser.dll, where as the previous version packs everything inside EO.WebBrowser.dll. As such you will need to reference EO.Base.dll and EO.WebEngine.dll.
If you have problem with adding the control at design time, please try to run GACTools.exe and add EO.Base.dll and EO.WebBrowser.dll into GAC. That may resolve the issue for you.
Thanks!
|
|
Rank: Newbie Groups: Member
Joined: 3/23/2015 Posts: 8
|
ok thanks for quick response. Works after setup as you suggest - just purchased the 2015 version. Is this info usually posted somewhere so I don't have to pester you kind support people with trivial things?
Previously in 2014 version you had a multi dll setup that was supposed to be faster and also you could specify a file cache. Do these things still apply.
Pages with things like HTML5, Bootstrap, Angular were very slow and buggy with the 2014 version so hopefully the 2015 version works better. Quite important as all our partners/customers are moving away from Java.
After a 5min test with the 2015 version it seems much better than the 2014 version. Still a bit slower than I'd like when you initially opening a page. Any tips to help with this?
Thanks
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,229
|
Hi,
Thank you very much for your business! We do not have a dedicated page that details the changes between 2014 and 2015. However the documentation for 2015 is updated so it contains updated information such as now it needs 3 DLLs instead of one. In any case, please do not hesitate to contact us if you have any questions. This is what we are here for.
The 2015 version no longer has a separate multi-DLL build. The initial reason that needed the multiple DLL build in 2014 was that instead of loading physical native DLLs from disk, we embed them in our .NET dll and dynamically load them on the fly. This gives us a lot of advantages but the loader we implemented in 2014 was slower comparing to the OS loader. This part has been significantly optimized in 2015 so in 2015 there would be no siginficiant difference on performance if we were to use the OS loader (thus would require the multi-DLL build). However another factor that also has an impact on performance is that we compressed the native code when we embed it into our DLL. This results in signficant smaller DLL size thus on some machines it actually has a performance advantage. However on some machine it does introduce a slight performance penalty due to the fact that the loader must uncompress the code first.
If the performance is still an issue for you, you can try to pre-create a hidden WebView using the ThreadRunner object in the background when your application starts. Or you can simply start a background application and creates a WebView there. The first method will intialize everything inside your process but it only works if your application does not need a WebView immediately after it starts. The second method will do the uncompressing part thus make subsequent application start faster since the uncompressed native code data is shared among all processes that uses the same version of EO.WebBrowser.
Hope this helps. Please feel free to let us know if you still have any more questions.
Thanks!
|
|