7

Here in this blog, they say that .net standard 2.0 it has a consistence state.

In the official web, it doesn't say if .net standard 2.0 is preview or final.

But I guess that .net standard 2.0 is in final version because EF Core 2.0 final is out, and this uses .net standard 2.0. Perhaps EF Core can be in final version and .net standard 2.0 is still a preview, but I guess it would be odd.

Also, is know that to use .net standard I have to use VS2017 15.3, that is in the 3rd preview version and it says it is not for production applictions.

So my question is, if .net standard 2.0 is consistence version (I don't know if this means final version) and EF Core 2.0 is final version too, but I need VS 2017 15.3 to use it but VS 2017 15.3 is not recommended for production, this means that then is it not a good option to use EF Core 2.0 final in production applications?

Thanks.

Álvaro García
  • 18,114
  • 30
  • 102
  • 193
  • Good question! And strange, except the updated nuget links, I don't see any EF Core 2.0 official announcement (the Roadmap still say *Under Development*), what is in there finally etc. – Ivan Stoev Aug 12 '17 at 10:42
  • 1
    One of the features important to me is GroupBy() which is still not available in EF Core 2.0 and has been pushed out to 2.1. See: https://github.com/aspnet/EntityFramework/issues/2341 – Con Kouroupis Aug 15 '17 at 00:59

2 Answers2

5

I think you should wait just a few days before the final version .NET core 2 & EF core 2

EF Core: https://github.com/aspnet/EntityFramework/wiki/Roadmap

The schedule for EF Core is in-sync with the .NET Core and ASP.NET Core schedule

NET Core: https://github.com/dotnet/core/blob/master/roadmap.md

ASP.NET Core https://github.com/aspnet/Home/wiki/Roadmap

Ship Dates

.NET Core 2.0 Q3 2017

.NET Standard 2.0 Q3 2017

Visual Studio 2017 Release Rhythm

https://www.visualstudio.com/en-us/productinfo/vs2017-release-rhythm

enter image description here

Update 15/08/2017: .NET core 2.0 + ASP.NET 2.0 + EF 2.0 + VS 2017 15.3 already released.

https://www.microsoft.com/net/core#windowscmd https://www.visualstudio.com/

Hung Quach
  • 2,079
  • 2
  • 17
  • 28
  • And do you know when will VS2017 15.3 be released? because if this final version of EF Core 2 and .net core 2 is near but VS2017 is not released and I need the 15.3 version to use them, perhaps what limits is VS2017 and not .net core or EF core. – Álvaro García Aug 12 '17 at 14:38
  • @ÁlvaroGarcía Updated. Take a look :) – Hung Quach Aug 12 '17 at 15:36
3

I think you are confusing .NET Standard with .NET Core. The former has been finalised but the latter is still in preview.

See also: .NET Standard vs .NET Core

Richard Szalay
  • 83,269
  • 19
  • 178
  • 237
  • Thanks. When I said that EF Core 2.0 is final, I mean Entityframework Core 2.0, not .net Core. Really I don't know the state of .net Core 2.0. My final goal is to use EF Core 2.0. .net Core is not my objetive. – Álvaro García Aug 12 '17 at 10:12
  • 2
    But your question relates to .NET Standard, which is just a spec (an "interface" in C# parlance). I'm just trying to point out that your question can't be answered in it's current state. Feel free to clarify and I'll update my answer if I can help. – Richard Szalay Aug 12 '17 at 10:15
  • Ok. Then I will change my question. What do I need to use EF Core 2.0 and if it is ready to use in production applications? – Álvaro García Aug 12 '17 at 10:18
  • 1
    That I unfortunately can't help you with, but I'll ping someone who can. – Richard Szalay Aug 12 '17 at 10:22
  • 1
    Essentially your question is "Can EF Core 2.0 practically be used in production considering it only has a .NET Standard 2.0 TFM but the tooling that supports that is still in preview?" – Richard Szalay Aug 12 '17 at 10:34
  • Yes, it is the question that I wanted to ask. You expose correctly. – Álvaro García Aug 12 '17 at 10:59
  • 1
    Hang in there for a couple of days – ErikEJ Aug 13 '17 at 09:03