Removing .NET 4.0 Support about conventional HOT 8 CLOSED

Seems like a good move to me, support for .NET 4 in the form of old releases should do the trick. Are you anticipating any major issues that might need to be backported or something?

from conventional.

I think it's a good idea. Every library that's ported to .NET Core is adding momentum in a positive direction (my opinion). Also I feel that because this is a test library, and you're bumping major version, there's less risk of pushing someone into an awkward situation.

from conventional.

I think the hardest part of getting my PR to Conventional ready was working out what was going on with the .csproj files and setting up all the links properly. It would definitely be nice to clean that up.

from conventional.

Onwards and upwards! I think if you leave a Nuget version around that is .NET 4.0 compatible no one can really complain (I.e. your 1.X version), and any new features only end up in the new one.

from conventional.

from conventional.

@KodrAus no big issues backporting that I could see, just didn't want to tick anyone off by doing it 'out of the blue'.

Looks like an overwhelming 👍 - so this shall be happening soon(ish)!

from conventional.

Will leave this open for a while longer to see if anyone else has a contrary opinion.

from conventional.

Half a year later... a status update!

It has been quite painful attempting to convert to netstandard - in particular the Reflection libraries only seem to be advanced enough in netstandard 1.5, and I suspect most people avoid 1.5 and 1.6 as odd anachronisms, and will be holding out for netstandard 2.

Current thinking is I'll await netstandard 2 dropping in Q3 2017, which will also give Cecil time to reach 1.0 with core support.

Closing this off for the moment, will reopen an issue with .NET Core support detailing plans separately.

from conventional.