Add support for newer frameworks

[md-amf1]

Do you have plans to migrate Dashing to netstandard2.0 and newer versions of .net core such as 2.1 and 3.1?

[markjerz]

So, the core library "Dashing" targets netstandard1.5 and .Net Framework 4.6 so it will (should) work in anything that comes after those.

There may be a slight issue with the Cli and Weaver libraries in that, if you don't have a matching .net core runtime, they may not work although I was under the impression it will try to run on a later runtime if one is available.

As the core library has very few dependencies I don't think there's any need to specifically support later targets (as that's usually done if supporting something later removes dependencies)

Are you coming across any particular errors?

[md-amf1]

Hi, sorry for the delayed response. In my experience, referencing netstandard versions < 2.0 generates lots of binding redirects and commonly causes versioning issues so we steer clear from it as much as possible. NET472 and netstandard2.0 get along very well though hence the reason I asked. I actually took a look at doing this myself when I first looked at your library but it unravelled a bit more than I had time for. I'm not against taking another look though if you thought it'd be helpful.