Should we move to VS2017?

[drewnoakes]

Now that VS2017's out, should we move to it?

Benefits would be:

• Ability to target multiple platforms with simpler csproj files, and a single solution/build
• Ability to use some C# 7 stuff (though without changing the public API, for now at least)

Any thoughts?

[somdoron]

I only hope Rider support new csproj file. Other than that I'm for it.

…

On Mar 21, 2017 10:59 AM, "Drew Noakes" ***@***.***> wrote: Now that VS2017's out, should we move to it? Benefits would be: - Ability to target multiple platforms with simpler csproj files, and a single solution/build - Ability to use some C# 7 stuff (though without changing the public API, for now at least) Any thoughts? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#648>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AClv9sIC7usHqDaiCIobeJNiXK0y6k9pks5rn5FXgaJpZM4MjgAV> .

[drewnoakes]

I didn't realise Rider wasn't there yet. Jura suggests initial support should be released any day in the next EAP: https://youtrack.jetbrains.com/issue/RIDER-3777

I migrated another project recently and the experience was relatively smooth. Will put a PR together for this too.

[drewnoakes]

Do we need to explicitly target monoandroid60? I'm not familiar with Mono/Xamarin development, and I don't have the tools installed (they're about 30GB in size IIRC). I'm getting compile errors due to this.

Seems Xamarin are moving towards .NET Standard support.

https://blog.xamarin.com/net-standard-library-support-for-xamarin/