Skip to content

Update DotnetEfNotFoundError sample to .NET 10 and EF Core 10 - #2330

Open
vladimir-pecanac-main wants to merge 1 commit into
CodeMazeBlog:mainfrom
vladimir-pecanac-main:seo/65706-ef-core-solve-command-or-file-was-not-found
Open

vladimir-pecanac-main wants to merge 1 commit into
CodeMazeBlog:mainfrom
vladimir-pecanac-main:seo/65706-ef-core-solve-command-or-file-was-not-found

Conversation

@vladimir-pecanac-main

Copy link
Copy Markdown
Collaborator

Moves the dotnet-efcore/DotnetEfNotFoundError sample to net10.0 and EF Core 10.0.13, pins System.Security.Cryptography.Pkcs 10.0.13 so the build no longer warns about the vulnerable 9.0.11 that SqlServer pulls in, replaces the get-only Customer class with the settable class the article shows (EF Core could not bind the old constructor, so dotnet ef failed against the sample), and adds a dotnet-tools.json manifest with dotnet-ef 10.0.13 so dotnet tool restore gets the tool the article uses.

Retarget to net10.0, move EF Core packages to 10.0.13, pin System.Security.Cryptography.Pkcs 10.0.13 to clear NU1902/NU1903, make Customer match the article (settable properties, no constructor) so dotnet ef can build the model, and add a local tool manifest for dotnet-ef 10.0.13.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant