Closed Nick-Lucas closed 7 years ago
This is probably a simple fix, much like #20. @kleberksms do you want to take a shot at it?
@Nick-Lucas would you mind checking if https://ci.appveyor.com/api/buildjobs/vrgpaoo3f4sg8537/artifacts/artifacts%2FSapientGuardian.MySql.Data%2FSapientGuardian.MySql.Data.6.9.816.nupkg resolves the issue for you?
Sure, I will need to do this on Monday, as it's a work solution. Will set a reminder now :)
Hey just wanted to say I haven't forgotten about this, I just need to get a few internal packages updated to run a test and should have some time tomorrow.
@SapientGuardian
Yep this appears to be working. I can't 100% guarantee my packages environment was the same, but based on what I know of the problem and your fix, I'd say it's sorted.
Thanks!
Thanks for checking. 6.9.816 should publish to nuget soon with the fix.
I have a netstandard1.3 class library using SapientGuardian.MySQL which is consumed in a WPF .Net 4.6.1 application.
After upgrading to
6.9.815
I can no longer connect to MySQL with the below error.After some digging it seems that .Net Standard and Core use Security Level 2 as standard, whereas .Net Framework uses Level 1.
It seems that the following commit has caused this regression: https://github.com/SapientGuardian/mysql-connector-net-netstandard/commit/95651617dea59470a155f0dfb9805a92154f2485
I have dropped down to
6.9.814
for now, since the difference is basically that one line of code.