Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to .Net Core 3.0 - dotnet ef is missing #18282

Closed
Pilchie opened this issue Oct 8, 2019 · 5 comments
Closed

Upgrade to .Net Core 3.0 - dotnet ef is missing #18282

Pilchie opened this issue Oct 8, 2019 · 5 comments
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@Pilchie
Copy link
Member

Pilchie commented Oct 8, 2019

From @ckruegerkpmg on Tuesday, October 8, 2019 8:38:52 AM

After Upgrades to .Net Core 3.0 dotnet ef is missing

General

After upgrading Visual Studio 2019 from 16.0/16.1/16.2 to 16.3 .Net Core get's upgraded to 16.3
All Projects that are useing Entitfy Framework are failing.

This helps: dotnet tool install --global dotnet-ef
BUT
global didn't install dotnet-ef for the machine globally, only for the user account.
A build Agent typically doesn't run in the same identity than the user that is installing Visual Studio.

It's very annoing that .Net Core 3 installation prevent building .Net Core 2.x Code in it's default installation.

Copied from original issue: dotnet/core#3570

@Pilchie
Copy link
Member Author

Pilchie commented Oct 8, 2019

From @scalablecory on Tuesday, October 8, 2019 6:09:15 PM

@Pilchie @livarcocc

@ChelseaKR
Copy link

I'm having this same issue as I'm trying to add this to my ,NET Core 3.0/2.2 apps - see #18276

@bricelam
Copy link
Contributor

bricelam commented Oct 8, 2019

You can also use a global.json file to continue using the 2.2 SDK in the project:

{
  "sdk": {
    "version": "2.2.402"
  }
}

@bricelam
Copy link
Contributor

bricelam commented Oct 8, 2019

(The 2.2 SDK includes dotnet ef so it should work as it used to without the need to install it separately)

@ChelseaKR
Copy link

Thank you @bricelam - seems to be working for my builds!

@ajcvickers ajcvickers added the closed-no-further-action The issue is closed and no further action is planned. label Oct 10, 2019
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported
Projects
None yet
Development

No branches or pull requests

4 participants