-
-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NetStandart Load with proxy problem #59
Comments
Hello @cacheoff , Thank you for reporting, We will look at this issue very soon. Best Regards, Jonathan |
Hello @cacheoff , A new version has been released v1.5.2-beta4, We removed some code that was calling await for nothing and make sure to add Let me know if we fixed Best Regards, Jonathan |
Hello Jonathan,
After hours of testing, i have noticed that the bug is not about your code. "Task.Run" statement never hits even when it includes only a line such as "var m = new HttpMethod("GET")". Therefore this is not a deadlock. I think this is a bug of System.Net.Http library in .NETStandart framework.
|
Which version of .NET Standard are you using? I don't remember the link, but I have heard of such issue in .NET Standard 1.3 Best Regards, Jonathan |
I was using .NetStandard 1.5. But because of that issue I converted my project to .NetFramework 4.6. Now i have no problem anymore. Everything works properly. |
Yup, that's why I released a version for .NET Standard 1.6 When I have asked to MysticMind (https://github.com/mysticmind/mysticmind-htmlagilitypack) which is the one that made almost all the code to support .NET Standard, he answering me this:
I still released a version for 1.3 since some people wanted to only use it without loading the HTML directly from the web. I will close this issue then since you moved back to .NET Framework 4.6 and anyway, I don't think there is something I can really do. Best Regards, Jonathan |
In a Task.Run statement when we use HtmlWeb.Load() with IWebProxy and ICredentials parameters Task.Run statement never hits.
The text was updated successfully, but these errors were encountered: