Welcome Guest Search | Active Topics | Sign In | Register

signalr problem in winform webbrowser Options
Vladimir
Posted: Thursday, October 27, 2016 9:23:53 AM
Rank: Newbie
Groups: Member

Joined: 10/27/2016
Posts: 4
Hi,
I have strange problem with page rendering inside of webbrowser. It is not always get events fom hub. in standard chrome everything is working. Also in WPF sample it is also working. Can you suggest what can be problem?
eo_support
Posted: Thursday, October 27, 2016 9:41:39 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

This is something you will need to work out yourself. We are not in a position to troubleshoot web pages for our customer. If you suspect the problem is on our side, you can try to isolate the problem to a test project and send the test project to us. See here for more details:

https://www.essentialobjects.com/forum/test_project.aspx

Thanks!
Vladimir
Posted: Thursday, October 27, 2016 9:48:42 AM
Rank: Newbie
Groups: Member

Joined: 10/27/2016
Posts: 4
mmm it is too difficult. May be you aware of some signalr issue to localhost? Also what is the difference between WPF and WinForm project? May be exist some parameters that I can assign?
eo_support
Posted: Thursday, October 27, 2016 9:54:28 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Vladimir wrote:
mmm it is too difficult. May be you aware of some signalr issue to localhost? Also what is the difference between WPF and WinForm project? May be exist some parameters that I can assign?


We do not do this kind of troubleshooting for our customer. We would like to help but we have thousands of customers and if everyone of them asks us maybe we know something that can help them debugging their application whenever they run into problems while using our product, we would be flooded with such requests and won't be able to function at all. As such we will only investigate if you have already put reasonable efforts on your end and can clearly demonstrate that the problem is related to us. Hope you understand.
Vladimir
Posted: Thursday, October 27, 2016 10:00:53 AM
Rank: Newbie
Groups: Member

Joined: 10/27/2016
Posts: 4
ok thanks - I will specify problem: what is difference in WPF and WinForm implementation?
eo_support
Posted: Thursday, October 27, 2016 10:11:17 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
There is hardly any difference at all on our part. The core class for EO.WebBrowser is the WebView class. This class load, run and display the page and this class is platform neutral.

Since EO.WebView has to sit somewhere in the UI, it requires a parent window handle. The only difference between WPF and WinForm is how this handle is created since in WPF it has to be created WPF way and in WinForm it has to be created Windows.Forms way. This is what the EO.WebBrowser.Wpf.WebControl and EO.WebBrowser.WinForm.WebControl is for. These two classes provide the "bridge" to integrate the core WebView class with your WPF or WinForm application. The bridge itself does not affect the functionalities since everything is done inside the WebView class. If you don't use Windows.Forms or WPF, you don't even need to those two "bridge" classes and you can just use WebView directly and your web page should still function the same way. So most likely the problem is not related to the difference between Windows.Forms and WPF. It has to be somewhere else in your code. That's why you have to try to isolate the problem in order to find out what triggered the problem first.
Vladimir
Posted: Thursday, October 27, 2016 11:05:14 AM
Rank: Newbie
Groups: Member

Joined: 10/27/2016
Posts: 4
I compared code from your WPF and found that exist assigning to e.UseOSHandler = true; in void WebView_LaunchUrl(object sender, LaunchUrlEventArgs e). What is it? Can you provide details?
eo_support
Posted: Thursday, October 27, 2016 11:12:32 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

See here for more details:

https://www.essentialobjects.com/doc/eo.webbrowser.launchurleventargs.useoshandler.aspx

Setting this property to true to automatically using the handler registered with the OS to handle the Url. For example, to automatically launch your email program to handle a "mailto:" Url.

Thanks


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.