Move to .NET Standard 2.0

ViktorHofer commented 6 years ago

What is missing:

_LINUX conditional compilation
build.sh, test.sh, .travis.yml files need to be adapted
module still active? if not just delete the .gitmodules file
nuspec (?) data into csproj

cc @danmosemsft

danmoseley commented 6 years ago

@adityapatwardhan the approach @ViktorHofer took here is to move to SDK style projects, and cross compile (project file here).

Another approach is to have dual projects, SDK style for .NET Standard/Core and regular style for .NET Framework. This is more "messy" but you retain all the features of the full .NET Framework project system, if you need them, and it is possible to work on the code without installing the .NET Core SDK.

I am curious whether you would have a preference between these two approaches. We are considering what guidance we want to give for such upgrades. Clearly, longer term we (Microsoft) should also aim to converge these so there's one single best way.

ViktorHofer commented 6 years ago

any feedback or response here?

ViktorHofer commented 6 years ago

MMI team I'm still waiting for a response. Please comment on the PR - if not, I will just close it.

PowerShell / MMI

Move to .NET Standard 2.0 #32