[RESOLVED] WebView2

[jdc20181]

I am implementing a simple app to load webmail for my new start up business, in its own app, I figured Webview2 would work since it seems to be supported for windows forms. What I can't seem to figure out is even after following the tutorial (exception is its vb) it still doesn't show up in the toolbox.

Is Webview for some reason only supported for C#? Am I missing something?

I am using 4.6.2, which should be still supported with that package. I have everything installed correctly, just seem to have the issue of getting it into existence.

Reference link: https://docs.microsoft.com/en-us/mic...arted/winforms

[ident]

https://stackoverflow.com/questions/...et-application

[jdc20181]

https://stackoverflow.com/questions/...et-application

That links to literally the same place I link to, and serves of no use to me or the issue at hand.

[passel]

Since it uses a library that is part of the Microsoft Edge (Chromium) Canary Channel installation to do rendering, you did install that first (one of the prerequisites) before NuGetting the Webview2 SDK, right?

Also, since you have C# available, even if you don't plan on using it, you could have gone through the C# procedures and see if it showed up in the toolbox when doing a C# winForm project.
If it shows up in the C# toolbox, but not in the VB toolbox, then perhaps there is an issues, although that doesn't seem likely. If it doesn't show up in either, than probably some prerequisite wasn't met.

[jdc20181]

Since it uses a library that is part of the Microsoft Edge (Chromium) Canary Channel installation to do rendering, you did install that first (one of the prerequisites) before NuGetting the Webview2 SDK, right?

Also, since you have C# available, even if you don't plan on using it, you could have gone through the C# procedures and see if it showed up in the toolbox when doing a C# winForm project.
If it shows up in the C# toolbox, but not in the VB toolbox, then perhaps there is an issues, although that doesn't seem likely. If it doesn't show up in either, than probably some prerequisite wasn't met.

Yeah I did that, turns out I kind of skipped a step, apparently NuGet skips out on preleases on default, so I finally got it taken care of, now my issue is regards to a borderless form not wanting to be draggable. I have tried a few different methods, but as long as the webview control exists, it don't work. I figure there is something in the control MS disabled, but not quite sure.

[passel]

Does the webview control fill the form, that is, you can't get the mouse to trigger MouseDown or MouseMove events to the form?
If so, does the webview control provide a mouseMove event?
I usually use code like the following, as it is all contained in the one event handler, to move a control or a borderless form.

  Private Sub Form1_MouseMove(sender As Object, e As System.Windows.Forms.MouseEventArgs) Handles Me.MouseMove
    Static lpos As Point
    If e.Button = Windows.Forms.MouseButtons.Left Then
      Me.Location += New Size(e.X - lpos.X, e.Y - lpos.Y)
    Else
      lpos = e.Location
    End If
  End Sub

[jdc20181]

Does the webview control fill the form, that is, you can't get the mouse to trigger MouseDown or MouseMove events to the form?
If so, does the webview control provide a mouseMove event?
I usually use code like the following, as it is all contained in the one event handler, to move a control or a borderless form.

I know *how* I use a similar piece of code that you have posted, it only does not work when the WebView control is filling the form. So after looking around looks like it does have its own mousedown event, so I tried to just repurpose my code, to be raised by the browser's mousedown but it doesn't seem to work once a web page is loaded.

It *is* in pre-release so, I imagine they already know this scenario - but couldn't be certain. I am going to try V1, and see if the same results occur. While EdgeHTML is not really a standard much many apps are still using it, so I will be back with my findings. May even contribute to the codebank if I find a way around it

Entirely different set of issues with V1 - so not even worth my efforts. but, I will figure out a way around this. ugh.