You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dotnet-ef package that is published for 8.0.1 requires the runtime version to be at least 8.0.1.
On some environments, like distros where .NET is source-built, it may take some days(/weeks) for that runtime version to become available.
This makes the dotnet install -g dotnet-ef command work, but subsequently invoking dotnet ef fail (due to the runtime version). The user can work around by explicitly specify the older version that matches the runtime version.
Could we relax the required runtime version for the global tools that are shipped in tandem with .NET through NuGet to not depend on a particular patch version?
The
dotnet-ef
package that is published for 8.0.1 requires the runtime version to be at least 8.0.1.On some environments, like distros where .NET is source-built, it may take some days(/weeks) for that runtime version to become available.
This makes the
dotnet install -g dotnet-ef
command work, but subsequently invokingdotnet ef
fail (due to the runtime version). The user can work around by explicitly specify the older version that matches the runtime version.Could we relax the required runtime version for the global tools that are shipped in tandem with .NET through NuGet to not depend on a particular patch version?
cc @baronfel @richlander
The text was updated successfully, but these errors were encountered: