Target .NET Standard 1.4 & 2.0 #370
Conversation
|
Why both? |
NuGet.config
Outdated
| @@ -4,5 +4,7 @@ | |||
| <add key="AspNetCore" value="https://dotnet.myget.org/F/aspnetcore-ci-dev/api/v3/index.json" /> | |||
| <add key="AspNetCoreTools" value="https://dotnet.myget.org/F/aspnetcore-tools/api/v3/index.json" /> | |||
| <add key="NuGet" value="https://api.nuget.org/v3/index.json" /> | |||
| <!-- TODO: Remove --> | |||
| <add key="dotnet-core" value="https://dotnet.myget.org/F/dotnet-core/api/v3/index.json" /> | |||
There was a problem hiding this comment.
Yes, just waiting for us to take the latest build... (hence blocked)
UWP. We hope to drop 1.4 ASAP. |
|
@bricelam @davidfowl Wait wait, are you planning to remove support for .NET 4.5.1 (and NetStandard 1.4 eventually) without any discussing with the community? Again? Only to have a possibility to remove a couple of lines of code? It is not serious. I think it is the same issue as MS had here: dotnet/aspnetcore#2022
|
|
@alexvaluyskiy There doesn't seem to be any discussion here about dropping .NET standard (which includes full netfx) - this is about changing to .NET standard 2.0. It's not the same thing as the notorious 2022 thread. |
| @@ -17,7 +17,7 @@ Microsoft.Data.Sqlite.SqliteException | |||
| Microsoft.Data.Sqlite.SqliteFactory | |||
| Microsoft.Data.Sqlite.SqliteParameter | |||
| Microsoft.Data.Sqlite.SqliteTransaction</Description> | |||
| <TargetFrameworks>net451;netstandard1.2</TargetFrameworks> | |||
| <TargetFrameworks>netstandard2.0;netstandard1.4</TargetFrameworks> | |||
There was a problem hiding this comment.
Because netstandard2.0 implies it. (Roughly)
There was a problem hiding this comment.
Because it's being replaced with .NET Standard 2.0, which is supported by .NET 4.6.1.
|
@willdean Look at the changes. They have removed support for |
|
@alexvaluyskiy They're replacing it with |
|
Yeh. Netstandard 2.0 is net461 min. This is not the same thing. |
|
@alexvaluyskiy across the board we don't plan to support older .NET Framework versions. .NET Framework 4.6.1 will be required in most if not all cases to use the newer versions of these libraries. |
|
@davidfowl I don't have any problems with net461. Just to announce it, that beforehand. Developers and the authors of libraries should know MS strategy. |
|
@alexvaluyskiy We officially announced that we're going to explicitly target .NET Standard 2.0 on the blog post and in the announcements repository aspnet/Announcements#243. So I'm not exactly sure what you're asking for. |
|
@alexvaluyskiy Almost all of the latest round of Microsoft libraries require .NET 4.6 or higher. Given that .NET Standard 1.4-2.0 all require 4.6.1 or higher (with tooling 2.0), and the announcement linked above, it's no surprise that you should be on or moving towards 4.6.1, 4.6.2, or 4.7. |
|
@davidfowl is it mean |
|
The announcement literally says this:
The blog post says "Our goal is to ship ASP.NET Core 2.0 on .NET Standard 2.0 so applications can run on .NET Core, Mono and .NET Framework". The announcement tries to go into more details but it really is all there... |
That's mean that all assemblies will target |
|
Also, all projects from |
We view the library as a bit crippled on .NET Standard 1.x. A good example is #313. Because |
|
moving from .net 4.5 to 4.6 is a nonissue for almost everybody. the change is fine, being able to do this sort of thing was the entire goal of ns2.0 |
Ideally, we'd just target .NET Standard 2.0, but since it will take a few months for UWP to support it, we'll cross-target 1.4 in the mean time. (See 64319de for the code we'll be able to remvoe.)
Blocked waiting on updates to KoreBuild
Resolves #350