Developer technologies | C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
WebBrowser.Navigate(pdfPath) fails after WIN Update
LemonXXX
1
Reputation point
Hi,
the last Microsoft Update
has broken the standard
WebBrowser.Navigate(pdfPath)
call, which allows to show a PDF preview within a Form.
I've been using this way for showing the preview because it worked easily for both x32 and x64 applications types.
Any suggestion for fixing it?
Please note that I'd like to keep that code and wouldn't implement this feature thru an alternative way (like using GhostScript).
T&R,
Piè
Developer technologies | C#
{count} votes
-
Viorel 125.7K Reputation points2021-06-10T14:32:21.923+00:00 What happens after WebBrowser.Navigate(pdfPath)?
By the way, there is a modern WebView2 browser control, which corresponds to new Edge browser.
-
LemonXXX 1 Reputation point
2021-06-10T14:43:02.05+00:00 The call returns a grey box instead of the preview:
I'll try to give a chance to
WebView2browser control.Thanks
-
Viorel 125.7K Reputation points
2021-06-10T14:58:13.97+00:00 Did you check if Internet Explorer, opened separately, is able to display this PDF file?
-
LemonXXX 1 Reputation point
2021-06-10T15:01:26.017+00:00 IE is able to show it.
-
Castorix31 91,506 Reputation points2021-06-10T15:05:30.393+00:00 You can also use the standard
Adobe Acrobat Browser Control Type Library 1.0 -
LemonXXX 1 Reputation point
2021-06-10T15:17:03.24+00:00 Does it work biside a x64 application?
-
Castorix31 91,506 Reputation points
2021-06-10T15:25:47.213+00:00 Hum...
It worked before...
but I just re-tested compiled as "x64", and I also get a grey box
(works as "Any CPU", tested on Windows 10 1909) -
Viorel 125.7K Reputation points
2021-06-10T16:13:04.527+00:00 If your application (or a simple test) works well in case of x86 configuration, then, since your form is simple, you can display it using a separate one-form x86 application, started with Process.Start. The form will be modeless. This is a temporary workaround.
-
LemonXXX 1 Reputation point
2021-06-11T09:11:58.093+00:00 @Viorel
I've implemented the WebView2 version.For doing it, I've followed the official MS guide: https://learn.microsoft.com/en-us/microsoft-edge/webview2/get-started/winforms
On my machine (the one I use for developing) it works like a charm.
However, I don't get how to make it working on another client.The guide speaks about prerequisites:
- https://developer.microsoft.com/it-it/microsoft-edge/webview2/
- https://www.microsoftedgeinsider.com/it-it/download
- .NET Framework version must be higher than 4.6
but I don't get if those are necessary for developing or running it.
Any idea?Thanks
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 7.000000000000001%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Daniel Zhang-MSFT 9,661 Reputation points2021-06-15T07:14:46.207+00:00
Sign in to comment
Sign in to answer