51Degrees.mobi-WebMatrix 3.1.12.6

Suggested Alternatives

FiftyOne.Pipeline.Web

Additional Details

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

There is a newer version of this package available.
See the version list below for details.
dotnet add package 51Degrees.mobi-WebMatrix --version 3.1.12.6
NuGet\Install-Package 51Degrees.mobi-WebMatrix -Version 3.1.12.6
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="51Degrees.mobi-WebMatrix" Version="3.1.12.6" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add 51Degrees.mobi-WebMatrix --version 3.1.12.6
#r "nuget: 51Degrees.mobi-WebMatrix, 3.1.12.6"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install 51Degrees.mobi-WebMatrix as a Cake Addin
#addin nuget:?package=51Degrees.mobi-WebMatrix&version=3.1.12.6

// Install 51Degrees.mobi-WebMatrix as a Cake Tool
#tool nuget:?package=51Degrees.mobi-WebMatrix&version=3.1.12.6

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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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 7,957 11/13/2018
3.2.20.2 3,404 6/4/2018
3.2.19.2 3,480 12/4/2017
3.2.18.2 6,731 9/13/2017
3.2.17.2 4,179 6/2/2017
3.2.15.6 3,980 3/20/2017
3.2.14.3 3,308 12/15/2016
3.2.13.5 3,731 11/1/2016
3.2.12.4 3,681 9/14/2016
3.2.11.1 3,474 8/18/2016
3.2.10.3-beta 2,266 6/22/2016
3.2.9.1 2,784 6/21/2016
3.2.8.1 2,917 5/23/2016
3.2.7.4 2,793 4/21/2016
3.2.7.3 2,771 4/4/2016
3.2.7-beta 2,396 2/12/2016
3.2.6-beta 2,210 12/7/2015
3.2.5.6 3,603 10/23/2015
3.2.5.5 2,789 10/16/2015
3.2.5.4 2,673 10/13/2015
3.2.5.3 2,474 10/12/2015
3.2.4.4 3,317 9/3/2015
3.2.3.2 3,284 7/21/2015
3.1.12.6 3,024 6/2/2015
3.1.11.1 3,132 3/20/2015
3.1.10.2 3,448 2/23/2015
3.1.9.3 4,833 1/8/2015
3.1.9.2 2,645 1/7/2015
3.1.8.4 2,831 12/4/2014
3.1.6.6 2,726 10/6/2014
3.1.4.5 4,983 7/10/2014
3.1.3.4 2,761 6/25/2014
3.1.3.3 2,867 6/24/2014
3.1.2.3 2,781 6/5/2014
3.1.1.12 2,702 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 between version 3.1.12.6 --

1. Modified TopDevices.cs in the Web UI namespace so that duplicated devices within the same HardwareFamily are removed. This results in a nicer looking user interface when multiple models in the same family are present.
2. Fixed Source.Dispose throwing an exception if a temporary data file could not be deleted. This should result in less temporary files being created.
3. When working in Stream mode the temporary file must be present for the data set to be created. This addresses a rare situation where after the temporary file is checked but before the data set is created another process could delete the temporary file resulting in a Lite data set being created.
4. WebProvider has been modified to augment Request.Browser with 3 additional pieces of information: MatchMethod, MatchDifference and MatchSignatureRank. All 3 can be used to check the level of confidence of the detector. I.e. when MatchMethod contains ‘exact’ the detector is confident that the user agent string in question corresponds to the matched device. If on the other hand the MatchMethod contains ‘none’ then the user agent is most certainly fake. For more information on all match methods please see: https://51degrees.com/support/documentation/pattern
5. Added the response text from the server to the error log when a data file update fails. This can help provide more information about why automatic updates have failed.
6. Results where Device-Stock-UA, X-Device-User-Agent or X-OperaMini-Phone-UA are present no longer generate an exception when interrogating signature rank.