This message is usually presented as a compatibility alert, not an error. This means that the package in question was developed to target that type of project and if any functionality is dependent on something unique to that platform, it may not work.
According to the Microsoft documentation on the subject:
The. NET Standard is the replacement for Portable Class Libraries (Pcls) [offering a more streamlined and lightweight form of platform-independent code sharing (different from PCL that is profiled to represent platform intersections). Also this new standard] is compatible with a subset of PCL profiles. O . NET Standard 1.0, 1.1 and 1.2 each overlap with a set of PCL profiles.
A quick google search should indicate some relevant results that explain this migration in detail, including major attention bridges, such as these:
How to make this plugin work being that Visual Studio does not give the option to create PCL projects and only . NET Standard
If you already have a project created in PCL format you should be able to use it normally. Otherwise, as stated before, it is likely that the plugin works normally in a project . Net Standard, despite the alert. If the behavior is different from that, the interesting thing would be to evaluate specifically the problems in question (certainly not a warning message).
How to make this plugin become compatible with my project.
As available at package info, the BLE 1.3.0 Plugin project is open source. To make it compatible you need to change the source code according to the project’s contribution policy including a release to support the new standard .Net Standard
. It will be necessary to have some domain over Nuget packages
I hope I’ve helped.