4 ms·
So...when do folks think it will be safe to use this? Often 1.0 is reserved for "we'll try to make less painful interface breaking changes after this release".
by wilde 10y ago
So...when do folks think it will be safe to use this? Often 1.0 is reserved for "we'll try to make less painful interface breaking changes after this release". But if this is any indication, we're still a ways off from API stability.
- WorldMaker 10y agoThe API is stable and worth building for. The remaining upheaval seems to be in tooling: how Visual Studio works with .NET Core projects and how command line/Linux/OS X works with projects. The existing tooling is alright enough that it is "safe" to use. This blog post reminds that the update to more final tooling should be somewhat seamless (VS will handle it for you automatically like any other project upgrade/migration; `dotnet migrate` will do the job for CLI and other platforms) and is on its way.
- manigandham 10y agoThis doesnt change anything with the API and NetStandard 2.0 coming soon will add back several missing APIs to .NET Core that are in the .NET full framework. .NET Core is safe to use right now, it's the IDE and command line utilities getting finalized for 1.0 release (of the tooling) so that it's easier to work with.