EO.WebBrowser 2019 For .NET V2019.2.91.0
.. and go to the .net framework folder and pick the.net sdk. i recommend picking the console version of the.net sdk and not.net core. it has a bunch of.net framework compatibility support for projects that are based on 1.0, 2.0, and 3.5 sp1. many of you already have.net core installed and that is a better option than the desktop libraries. you will also notice the more modern “empty” folder structure that the.net sdk should be using. you can also choose to do any of the other version of the.net sdk if you wish to.
.. and then build your project. if you’ve done a lot of customization in your project it’ll probably just build because it knows where everything is. but it took a few things to get this fully converted.
as you’ve probably guessed, the easiest way to do this is to just drop the.net core sdk into the project. you don’t have to do anything special to do this. just select the folder that contains your project and drag it to your project. you’ll notice that the new.net core project magically added all of your files. all you’ll need to do is delete the.net 3.5 project files that are below the.net core project.
there’s two ways to add asx files to a.net core project. the first is to drag in the.asx files into your.net core project and build the application. the second is to create an asx package file and add that. the key here is to create a package file that contains the binary files. the fact that you have the.net project file means the project builds and you can drag the files into your. it will find them because it has the.aspx file and uses that to locate the binaries. make sure you leave the default options of “create directory for webform/aspx/asmx” and “do not copy content”.
one of the downsides of the new.net core framework is that it doesn’t have an official version of the webbrowser control. as much as i prefer the.net framework version because it’s just there, and pre-installed, there are many cases where you just want something that just works and isn’t mucked up by.net framework pre-installed components. one of those areas is parsing the html dom, and generating the css styles. the dom can be very complex. it’s possible to get yourself into trouble trying to parse it all from scratch, and everything is so deeply entangled that a developer would need to understand the full power of the dom to get a correct result. that’s hard, and too deep for anyone but a professional. using an off-the-shelf parser really simplifies things. for that reason i developed a set of classes for.net which simply parse the dom for you and generate the css for you. these classes have been available for years and years with the release of.net framework, but the internal version numbers were always misleading. i finally decided that given the relative complexity of the html dom it was time for the classes to get their own version numbers.
i’ve been using the classes for years, and certainly they’re still under active development. in fact, the older the versions are the faster they are, which really shows the benefit of making changes incrementally to follow the .net core guidelines about compatibility and versioning. the worst that can happen is that you will run out of older versions of the library which will still work correctly.
looking for more capabilities? eo.webbrowser offers ability to customize its features by passing settings and options. you can customize the home page, page title, history and even the advertising settings! you can also easily integrate additional apis using custom code button. for example, you can easily integrate google web fonts or dotnetzip api