uap-csharp icon indicating copy to clipboard operation
uap-csharp copied to clipboard

C# implementation of ua-parser

Results 11 uap-csharp issues
Sort by recently updated
recently updated
newest added

General upgrade of the embedded regexes from the submodule.

This idea for this PR is based on #60, but it just extracts all nested classes to their own files (`CTRL + .` and "Move to xx.cs"). this is common...

I'm not sure if this is the right place to ask this question since it affects multiple implementations, including this. I [cross-posted to the uap-core project](https://github.com/ua-parser/uap-core/issues/510) but sharing here just...

I installed the package on the .net core and has received other for os and browser and other properties

Before ![image](https://user-images.githubusercontent.com/22498629/81099126-13596e00-8f13-11ea-8496-c72791f27d86.png) After ![image](https://user-images.githubusercontent.com/22498629/81098941-c70e2e00-8f12-11ea-8ef4-e66257d9e95c.png) BenchmarkDotNet=v0.12.1, OS=Windows 10.0.18363.815 (1909/November2018Update/19H2) Intel Core i5-3230M CPU 2.60GHz (Ivy Bridge), 1 CPU, 4 logical and 2 physical cores .NET Core SDK=3.1.201 No breaking changes

We would be very grateful if we could have a NuGet release targeting .NET Standard 2.0? Any chance?

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43 The family is reported as chrome instead of edge

Is there a way to get the device type? Like `mobile`/`tablet`/`desktop` or something like that? My goal is to understand if the client is a mobile phone. Thanks.

If you run this on a windows 11 os, the nuget will say it is windows 10. ![image](https://user-images.githubusercontent.com/87320487/208092866-d501190c-3d88-40e6-a095-00e6b985454b.png) ![image](https://user-images.githubusercontent.com/87320487/208092971-eaf12c8b-10e0-44a9-8139-20861f4bdd69.png) ![image](https://user-images.githubusercontent.com/87320487/208100666-d0530483-25be-4fd0-8aae-7e3b302516a3.png)

I’ve encountered a significant performance issue with UAParser when it’s used in a logger. The issue arises when Parser.GetDefault() is called repeatedly during large operations. Each call to the logger...