Hello Karl,
FFF wrote:i'd suppose, Dick asks for a replacement of the functionality, not the resurgence of finally dead IE...
Indeed that is what I am looking for.
I have a document module in my program. I can connect any file with a relation and when I click on the browser with linked documents the program executes a
Code: Select all
SELF:oPreview:CreateEmbedding("Shell.Explorer")
where oPreView is an OLE Webbrowser displayed in one of the panes of a splitwindow.
Some documents show within the control itself, like a Word document or a JPG file. Some however open in the program where the file extension is associated with, this can depend on the settings. A PDF for example always opens in PDF X Change Viewer (this is because the NPAPI they use is no longer supported in e.g. Firefox ).. An AEF would open in VoPP, an MP4 opens in VLC Media Player.
If I directly type the filepath in Firefox, I sometimes get a different behavior, in the above examples the doc(x) file opens directly in Word instead of in the browser. Firefox asks me if it should open the file in the specific software or save it.
E.g. the MP4 / PDF / JPG are directly displayed within Firefox.
Chromium based Vivaldi, which is my alternative browser, is doing the same as Firefox.
I expect a similar difference in behavior when I would use WebView2. Difficult to say which is preferable, and if any extension would work in Webview2 (directly or via the software package). Perhaps WebView2 is fine/better for all file formats. But that's why I wondered if there's a DotNet alternative to Shell.Explorer.
Finally, I think it's a but confusing that it's called Shell.Explorer.. It suggests that Windows Explorer is used, not an ancient Internet Explorer.
Dick
