Two calls, services.AddFiftyOne(Configuration) and app.UseFiftyOne(), put Device Detection and IP Intelligence results on every ASP.NET Core request, read through IFlowDataProvider. Elsewhere, DeviceDetectionPipelineBuilder picks UseOnPremise for a local file or UseCloud for a hosted call, and data.Get<IDeviceData>() returns typed values.
FiftyOne.Pipeline.AgentSignature checks the IETF Web Bot Auth signature an automated agent sends, and FiftyOne.Did checks a 51Did is genuine. Human Confidence and Identifiers are answered by the cloud service, and a demo of the Preference Management Platform (PMP) shows a visitor's choice reaching the 51Did.
dotnet add package FiftyOne.DeviceDetection
dotnet add package FiftyOne.IpIntelligence
Code and issues: https://github.com/51Degrees/51degrees-dotnet
Documentation: https://51degrees.com/documentation/index.html?utm_source=sourceforge&utm_medium=listing&utm_campaign=51degrees-dotnet&utm_content=description&utm_term=docs
Features
- ASP.NET Core middleware with AddFiftyOne and UseFiftyOne
- ASP.NET on .NET Framework with FiftyOne.Pipeline.Web.Framework
- Device Detection and IP Intelligence in-process or in the cloud
- Typed results through IDeviceData
- Web Bot Auth checks with FiftyOne.Pipeline.AgentSignature
- Reverse geocoding with FiftyOne.GeoLocation
- Access to Human Confidence and Identifiers in the cloud service
- FiftyOne.Did to read a 51Did and check it is genuine
- Open source, EUPL 1.2