Removed net462 from test project

[abergs]

Running ```dotnet test`` generates a bunch of errors if net462 is targeted.

[MeikTranel]

What kind of errors?

[abergs]

System.TypeLoadException : Could not load type 'System.Security.Cryptography.ECPoint' from assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Stack Trace:

[MeikTranel]

That's the error i told you about here: MeikTranel/MigrationSupport#1 (comment)

The issue is that .NET Standard 2.0 has APIs that .NET v4.6.2 doesn't have, but the .NET team still marked 4.6.2 as .NET Standard 2.0 compatible. One of the 43 APIs missing is the one you have here (https://github.com/dotnet/standard/blob/master/docs/comparisons/netstandard2.0_vs_net461/System.Security.Cryptography.md); which is why your test fails on .NET462. Because you produce .NET Standard packages this means that there can be consumers of your package using .NET 4.6.2, that will eventually hit this bug. That's why i added 4.6.2 in the first place.

[MeikTranel]

I just checked. There's a nuget package that can help you avoid this scenario.

[MeikTranel]

Let's try to avoid this. I will test things locally to fix this problem differently.

[abergs]

Hmm. I see. Well. We either take on a dependency (maybe Source Include this as well?) or add a disclaimer that net.462 is not supported due to this issue (not very nice)

[MeikTranel]

Well the dependency would only exist for the net46X depedency group, not for the main netstandard2.0 dependencygroup.

[abergs]

I believe the failing test is due to #32

[aseigler]

I will be fixing #32 soon. Just been considering the best way to do it.

[aseigler]

This should be clean now.

[abergs]

@MeikTranel Do you think we should avoid removing net462?

@aseigler It does passes in the CI now. Good work.

[MeikTranel]

Sorry, christmas chores came first 😄
We should at least try to make it sane. I was thinking we put a net461/net462 depedency group in there which has some msbuild targets erroring when you're trying to build it with net461 or net462.
Because the additional nuget dependency might not be such an easy task.

[MeikTranel]

I just cooked something together locally. This appends a task to BeforeBuild that checks if the current targetframework is one of the offending frameworks and puts a big ol' error out.

We can put a help url and better text in there of course.

[abergs]

@MeikTranel Looks really good! Send a PR? :) And good idea to link to an issue at github (or a net462.md file) in the repo.

[MeikTranel]

Will do but tomorrow tho. Already back into Christmas Dinner Madness V2 😂