You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with a scenario where I want to load a custom request into an image tag on a web page, and the image is to be generated by the C# app hosting the WebViewControl.
In my app set up, I have the following:
In javascript code in the page loaded into the control, I have this javascript
When the resource is requested by the page, the event handler in my app is fired (As Expected), my C# code in the handler looks like this
When the handler runs, this seems to set ok, no errors, no compile time problems etc, but soon after the entire app stops at the main entry point with a null reference.
If I breakpoint on my handler app, and inspect the event object just before it returns, you can clearly see that "e.Response" is null, despite my code assigning a value to it.
It seems to me that this is the correct process for handling a web resource request, can the team confirm if it is?
I'm currently working in .NET 4.7 with a WinForms app, but have been testing in Core too.
The text was updated successfully, but these errors were encountered:
shawty
changed the title
Cannot set the response type in a web resource request event
(Suspected Bug) Cannot set the response type in a web resource request event
Jun 10, 2020
I'm working with a scenario where I want to load a custom request into an image tag on a web page, and the image is to be generated by the C# app hosting the WebViewControl.
In my app set up, I have the following:
In javascript code in the page loaded into the control, I have this javascript
When the resource is requested by the page, the event handler in my app is fired (As Expected), my C# code in the handler looks like this
When the handler runs, this seems to set ok, no errors, no compile time problems etc, but soon after the entire app stops at the main entry point with a null reference.
If I breakpoint on my handler app, and inspect the event object just before it returns, you can clearly see that "e.Response" is null, despite my code assigning a value to it.
It seems to me that this is the correct process for handling a web resource request, can the team confirm if it is?
I'm currently working in .NET 4.7 with a WinForms app, but have been testing in Core too.
The text was updated successfully, but these errors were encountered: