prep move to NET Standard 2

[mauroservienti]

Connected to #258

• Upgraded to new project format
• Removed all versions and add support for .NET 4.6 and netstandard2.0
• Command line build support via BullsEye
• Simplified AppVeyor configuration
• Removed Topics from namespaces and artifacts names
• move to .NET 4.7.2 only in light of supporting NET Standard 2 Not needed to just go straight to NET Standard 2

[micdenny]

Why support only 4.7? There are new framework features you would like to use in radical? Something related to performance that we can take advantage only if we compile against 4.7?

[mauroservienti]

Because it’s the only one that can reliably support netstandard2 that is the next move in light of the fact that necore3 will support WPF.

[mauroservienti]

[mauroservienti]

In theory we could add multi targeting support to go back to 4.5. Is there any good point to add that burden?

[mauroservienti]

If we really want to support 4.5.2 (that is the oldest supported version of the full framework) we could multi-target net452 and netstandard2 so that people on old OS versions can still use Radical without any dramatic change.

[micdenny]

Probably that’s fine to go only with one target, old fx will stick to old radical version like we will do for some time