DotNetBrowser.Chromium.Win-x86
Solution for integration of Chromium-based component into .NET applications.
| Version | Released | Deprecated |
|---|---|---|
| 2.15.1 | Jun 17, 2022 | Aug 8, 2022 almost 2 years ago |
| 2.15.0 | Jun 14, 2022 | Aug 8, 2022 almost 2 years ago |
| 2.14.0 | Apr 29, 2022 | Aug 8, 2022 almost 2 years ago |
| 2.13.1 | Apr 12, 2022 | Aug 8, 2022 almost 2 years ago |
| 2.13.0 | Apr 7, 2022 | Aug 8, 2022 almost 2 years ago |
| 2.12.0 | Mar 23, 2022 | Aug 8, 2022 almost 2 years ago |
| 2.11.0 | Jan 14, 2022 | Aug 8, 2022 almost 2 years ago |
| 2.10.0 | Nov 18, 2021 | Aug 8, 2022 almost 2 years ago |
| 2.9.0 | Sep 24, 2021 | Aug 8, 2022 almost 2 years ago |
| 2.8.0 | Aug 20, 2021 | Aug 8, 2022 almost 2 years ago |
Last updated on 19 January-2024, at 02:16 (UTC).
Got EOL?
Xeol can give you visibility into end-of-life (EOL) and deprecated packages across all your repositories. Try it out!
Description
The Chromium-based 32-bit binaries for DotNetBrowser. To be able to use DotNetBrowser, you should obtain a licence by filling a form at https://www.teamdev.com/dotnetbrowser#evaluate
FAQs
> Is DotNetBrowser.Chromium.Win-x86 Deprecated?
It appears there are some versions of DotNetBrowser.Chromium.Win-x86 that are deprecated.
> What is the deprecation date for the latest version of DotNetBrowser.Chromium.Win-x86?
The latest version of DotNetBrowser.Chromium.Win-x86 was released on Jun 17, 2022, and it is now deprecated.
> What does deprecated mean?
Deprecated means that the package was either marked as deprecated on the package registry, or that the source code repository for the package was archived.