I was wondering if anyone knows what is going to happen with the win forms browser control in the .net framework after IE 11 support is dropped next month. From my understanding the browser control uses an IE shell, but if IE is no longer supported what will happen? are we just SOL? are the porting it to use Edge? just wondering if anyone has heard, I cant seem to find any info. Thanks!
Microsoft is not discontinuing support for IE 11; they're simply not developing another version of IE. According to Lifecycle FAQ—Internet Explorer and Edge:
"Internet Explorer 11 is the last major version of Internet Explorer. Internet Explorer 11 will continue receiving security updates and technical support for the lifecycle of the version of Windows on which it is installed."
Therefore, the answer is:
"The Winforms Browser control will keep working the same way it was before."
Related
webBrowser bug
I want to join youtube with web browser , but I get this message,any idea?
the browser used in visual studio is just IE (Internet Explorer) and since most websites doesn't support IE anymore, most popular sites like YouTube, Twitch, amazon, stack overflow ;) etc. use modern elements and the html/js/css in the website may not work with IE, so most websites either try to load the website or just show a "You need to update your browser version screen" (what you are experiencing right now)
EDIT: i found how to use Webview (not IE) so websites can work properly
https://blogs.windows.com/msedgedev/2018/05/09/modern-webview-winforms-wpf-apps/
(NOTE: This is WebView1, Not The Newer WebView2, Please See quaabaam 's answer, here is the link for the answer he/she gave "
Web Browser Control & Specifying the IE Version")
(NOTE 2: this link is from 2018 and its been 4 years now so im unsure if the code sample on the Microsoft blog post will work, this is due to .NET 6 and how it changes how you make methods and many more stuff)
We have a service to manage some custom desktops using the user32.dll SetThreadDesktop and SwitchDesktop methods. Everything has been working well until Windows 10 version 1709 arrived.
With this Windows 10 version (or later), when EnableLUA is activated (when we have a custom desktop active), if the user locks his session, the winlogon desktop doesn’t appear and our custom desktop remains visible (though it isn’t possible to interact with it) until the user presses the combination CTRL+ALT+DEL.
It seems like the winlogon desktop is not able to stay topmost over our custom desktop. I didn't find any information about this, so is this a possibility? Could anything else be going on?
PD: Same scenario on Windows 10 version 1607 device works well.
Microsoft recognized the bug and they will solve it. The error is reproducible with the Sysinternals Desktops tool (currently belonging to Microsoft).
Waiting for an update that fix it...
I'm developing a WPF application using Cefsharp. This web browser inside the app should show some flash contents. I found some forum where the users suggest to use papi flash or pepper flash for Cefsharp.
I have no idea how to implement those plugin in my project.
I'm using the last version of Cefsharp.
Someone can explain how to enable Flash contents in my webview?
Thanks
You need to download the PPAPI version of Flash. Every computer running your app must do the same. Visit http://get.adobe.com/flashplayer/otherversions/ and select FP [xx] for Chromium and Opera where [xx] is the current version number, which is 26 at the time of this answer.
I'm developing an MVC app.
If I (on my Surface Pro) goes to http://www.whatbrowser.org/ it correctly says IE 10.
But if I go to my MVC app and print out the Request.Browser.Version, it returns 7.
Any idea why? Is Request.Browser.Version broken?
Thanks
Some of this is touched on in Detect Internet explorer browser version problems.
Last I knew Request.Browser uses the *.browser files that come with the installs of ASP.NET, and easily get out of date. Microsoft releases updates to them every so often, but not often enough. Currently there are some issues with webform pages breaking on IE10 without updated browser files.
Like the comments have said, browser detection is very broken. If you need to detect the browser, at the very least shy away from using the user agent string, and seriously consider why you need to know exactly what browser is used.
Request.Browser.Version doesn't always return the 'correct' browser version for IE because of many factors including compatibility view, meta tags etc.
You would be better off detecting browser capabilities instead. Further reading here: http://msdn.microsoft.com/library/3yekbd5b
As a personal preference, it would be best to detect the OS instead of the browser. Most of the common HTML5/CSS3 features are supported in IE9 and above and IE9 requires Windows Vista and up. The best way to do this using the User Agent is by checking the Trident. If there is compatibility view enabled via the browser or by using meta tags by the app itself, the wrong 'version' is returned but the Trident remains correct.
PS. This isn't fool proof but this would work most of the time.
Further reading about Trident here: http://msdn.microsoft.com/en-us/library/ms537503(v=vs.85).aspx#PltToken
Does anybody know if there is some sort of bug or issue with the webBrowser activex control in .NET applications, in this case the embedded browser loads a web page that depends on javascript to play music previews. It works once but if you navigate to a new page in the system it stops working.
Viewing the same site in just a normal IE browser results in no errors at all (tested on several systems of various types).
It happens on several different OS's, XP 32 and 64 bit, Vista, Windows 7.
Its also not a java applet, just jQuery and the longtail video player with some JS to bind a preview link to the player. Im very confused as to why it works sometimes but not others.
Its also a large live system and getting lots of complaints.
Let me tell you this straight up. The default rendering engine on the WebBrowser control is fixed to ensure compatibility across all platforms.
Basically, if your installed browser is IE 7 - IE 9, then the rendering engine used is IE 7.0 only (by default).
If, however, your installed IE version is IE 6 or below, then the rendering engine used is IE 4.0, unless of course you set it otherwise.
There is a misconception that WebBrowser control uses whatever is currently installed (current IE version) but this is not true, since they do this to reduce backward compatibility issues. You can see (as proof) that this really is your problem by going to http://www.whatsmyuseragent.com in your normal browser, and then going to that website again in your WebBrowser control, you will see that it says MSIE 7.0 :).
I suspect your users (and you) who are on IE 6.0 would be experiencing the problems you've alluded to since their rendering engine being used is IE 4.0 (and IE 7 if they are running anything between IE 7 to IE9). This is really bad, especially if they are on IE 6, you should ask them to upgrade their browser if they are IE 6, then, IE 7.0 will be used regardless.
I'm not sure if, when IE 10.0 comes out, the WebBrowser control's default engine will go to 10.0 (if 10.0 is installed on system of course) or if it will remain as IE 7.0 even after IE 10.0 is released, we will have to see once it comes out. However, if we guess based on previous experience, I suspect IE 10.0 will be the last version that uses IE 7.0 rendering engine, and when IE 11 comes out, the default rendering engine will remain as IE 11 for all versions of IE between IE 11 & IE 14. This is just a guess by extrapolating what they've done in the past.
You can set the WebBrowser control to use the current installed version of Internet Explorer; if you want more information on how to do this, or how to further fix the rendering engine, let me know and I'll help you out with it.
Which version of .net are you using?
Also which OS?
Ive noticed within Vista that Java applets <applet> tags causes catastrophic issues. I believe this is due to it using Microsoft JVM for its java processing, which happens to be unsupported now. This does not occur in XP from what ive seen
The web browser control uses the same shell as the installed version of Internet Explorer, but in my experience, the full browser handles things more gracefully.
It is worth adding some debug to the JavaScript to see where the problem is - is it because longtail isn't registering as loaded, so no events are binding or is it because of a problem with the events.