51Degrees.mobi-WebMatrix
3.1.11.1
51Degrees.mobi-webMatrix is no longer maintained by 51Degrees. We will continue to produce paid-for data files, but will not be making any updates to the code. The replacement 'version 4' packages improve performance, support User-Agent Client Hints and have a more modern API. See our pricing page for options: http://51degrees.com/pricing
See the version list below for details.
dotnet add package 51Degrees.mobi-WebMatrix --version 3.1.11.1
NuGet\Install-Package 51Degrees.mobi-WebMatrix -Version 3.1.11.1
<PackageReference Include="51Degrees.mobi-WebMatrix" Version="3.1.11.1" />
paket add 51Degrees.mobi-WebMatrix --version 3.1.11.1
#r "nuget: 51Degrees.mobi-WebMatrix, 3.1.11.1"
// Install 51Degrees.mobi-WebMatrix as a Cake Addin #addin nuget:?package=51Degrees.mobi-WebMatrix&version=3.1.11.1 // Install 51Degrees.mobi-WebMatrix as a Cake Tool #tool nuget:?package=51Degrees.mobi-WebMatrix&version=3.1.11.1
The fastest, most accurate tools. Deployed by millions.
Request.Browser properties will be populated with data from 51Degrees Lite Device Data. Other features
include automatic image optimisation, monitoring of network conditions and client side feature detection.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET Framework | net40 is compatible. net403 was computed. net45 was computed. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
- Microsoft.Web.Infrastructure (>= 1.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last updated | |
|---|---|---|---|
| 3.2.21.1 | 9,351 | 11/13/2018 | |
| 3.2.20.2 | 3,636 | 6/4/2018 | |
| 3.2.19.2 | 3,684 | 12/4/2017 | |
| 3.2.18.2 | 7,276 | 9/13/2017 | |
| 3.2.17.2 | 4,495 | 6/2/2017 | |
| 3.2.15.6 | 4,218 | 3/20/2017 | |
| 3.2.14.3 | 3,567 | 12/15/2016 | |
| 3.2.13.5 | 4,003 | 11/1/2016 | |
| 3.2.12.4 | 3,952 | 9/14/2016 | |
| 3.2.11.1 | 3,764 | 8/18/2016 | |
| 3.2.10.3-beta | 2,368 | 6/22/2016 | |
| 3.2.9.1 | 2,898 | 6/21/2016 | |
| 3.2.8.1 | 3,025 | 5/23/2016 | |
| 3.2.7.4 | 2,900 | 4/21/2016 | |
| 3.2.7.3 | 2,841 | 4/4/2016 | |
| 3.2.7-beta | 2,487 | 2/12/2016 | |
| 3.2.6-beta | 2,302 | 12/7/2015 | |
| 3.2.5.6 | 3,772 | 10/23/2015 | |
| 3.2.5.5 | 2,889 | 10/16/2015 | |
| 3.2.5.4 | 2,767 | 10/13/2015 | |
| 3.2.5.3 | 2,550 | 10/12/2015 | |
| 3.2.4.4 | 3,415 | 9/3/2015 | |
| 3.2.3.2 | 3,376 | 7/21/2015 | |
| 3.1.12.6 | 3,104 | 6/2/2015 | |
| 3.1.11.1 | 3,221 | 3/20/2015 | |
| 3.1.10.2 | 3,517 | 2/23/2015 | |
| 3.1.9.3 | 4,926 | 1/8/2015 | |
| 3.1.9.2 | 2,731 | 1/7/2015 | |
| 3.1.8.4 | 2,909 | 12/4/2014 | |
| 3.1.6.6 | 2,788 | 10/6/2014 | |
| 3.1.4.5 | 5,064 | 7/10/2014 | |
| 3.1.3.4 | 2,844 | 6/25/2014 | |
| 3.1.3.3 | 2,929 | 6/24/2014 | |
| 3.1.2.3 | 2,864 | 6/5/2014 | |
| 3.1.1.12 | 2,780 | 5/27/2014 |
Important: Upgrading users of Enhanced Data need version 3.1 format data.
Device detection algorithm is over 100 times faster than version 2. Regular expressions and levenshtein distance calculations are no longer used.
The device detection algorithm performance is no longer limited by the number of device combinations contained in the dataset.
Two modes of operation are available:
Memory – the detection data set is loaded into memory and there is no continuous connection to the source data file. Slower initialisation time but faster detection performance.
Stream – relevant parts of the data set are loaded into memory when required and cached to improve performance. Rapid initialisation time but approximately 50% slower detection performance. This mode is used when operated in a web environment.
JPG and PNG format images can be optimised to improve performance.
Bandwidth and response times can be monitored to understand in real time the end users experience.
Feature detection is used to override properties in the data set to provide details such as iPhone model or the screen orientation. These values become available to the server from the 2nd request from the device onwards.
Multi-threading is no longer used within the matching algorithm.
When used in a web environment the detection results are stored within the session when available and are no longer cached separately.
-- Changes for 3.1.11.1 --
1. Changed Evaluate method of Controller to include the 0 index character
to ensure Exact matches are returned for useragents that have nodes at the
0 index position. Reduces the number of times Nearest methods are used when
Exact should be used.