The issue is that some libraries, like Segment, might not need conflicting libraries, whereas Sentry was compiled against a newer version of certain libraries shared with the host application.
If Segment uses the same or older libraries, binding redirects will work normally since they usually look something like
0.0.0.0 - CurrentVersion -> CurrentVersion
But if you try to use a library that uses something newer than CurrentVersion, Binding Redirects may stop working properly.
There are also some issues specific to .NET Framework due to mistaken versioning. A few standard libraries were impacted by this including System.Net.Http but others are possible. The issue was caused by the NuGet packages having higher version numbers than the inbuilt version, but their assembly version number was lower than the version that comes with the framework.
i.e. the framework library might have a 126.96.36.199 version of the library, with a NuGet package versioned 188.8.131.52, but the actual DLL inside the NuGet package had 184.108.40.206 as the version. Something like this can also cause a binding redirect issue on .NET Framework, because NuGet won’t install the package since the assembly version of the NuGet package is lower, but then the application looking for it anyway because the NuGet version number is higher.
That being said. Look for the app.config inside the application, not in your 3rd party package. The host application also has to have an app.config, and that is the one that your plugin will actually use, not whatever you use in your project.