search

dotnet / standard

This repo is building the .NET Standard
3.07k stars 428 forks source link

netstandard20 portability on .NET Core #32

Closed johnbraden closed 8 years ago

johnbraden commented 8 years ago

We've developed a library for the .NET Core framework with the build target netstandard1.6. It can be executed in Windows, Linux and Mac OS. If we update to netstandard20, will it work on all platforms?

Project: https://github.com/blackcity/backload Website: https://www.backload.org

benaadams commented 8 years ago

I assume not currently as only .NET 4.6.1+ will currently support netstandard20 - though it will eventually. More details here https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/

johnbraden commented 8 years ago

Thanks. But what does this mean for platform portability? Currently our library supports Linux and Mac OS with netstandard1.6 target on .NET Core (resp. ASP.NET Core). When .NET Core moves to .NET Standard 2 can it be executed on these platforms? Or do you give up platform portability for .NET Core in order to become .NET Standard 2 compatibile faster? I have some doubts that .NET Standard 2 will ever come to Linux and Mac OS.

benaadams commented 8 years ago

Do you need .NET Standard 2.0? For example if you target .NET Standard 1.3 that will give you wider cross platform compatibility now (including Mono, UWP, iOS, Android and Core) whereas 2.0 will be in the future and .NET Standard 1.3 is automatically compatible with 2.0.

davidfowl commented 8 years ago

.NET Standard 2.0 does not take away .NET Core's ability to run on multiple OSes. The blog post didn't call it out explicitly but nothing is going away.

johnbraden commented 8 years ago

@benaadams @davidfowl Thanks both of you for this clear statement.

weshaggard commented 8 years ago

Correct on both fronts. There isn't any thing inherit in .NET Standard 2.0 that makes it not implementable in x-plat. There will always be some rough edges of APIs that won't work well x-plat and might even throw PlatformNotSupportedException those should be the exceptional case.

As for corefx/.NET Core support .NET Standard 2.0 see https://github.com/dotnet/corefx/issues?q=is%3Aissue+is%3Aopen+label%3Anetstandard2.0 which are all the issue tracking the work do add that support.