MVC Scaffolding does not support the Entity Framework 6 or later as a few tips for NuGet

Because of the limitations of the visual Library Package Manager, there are a number of features that are needed that cannot be done in the interface.

The following tips need to be done using commands in the Package Manager console.

First, after changing the project target framework, update the package

When you change the target framework of a project, whether it is an upgrade or a downgrade, the component referenced in the project is not the most appropriate version of the framework, and NuGet automatically appears with a warning prompt to re-update the component, and the action is to point to an English page where the key parts of the page are directly recorded:

Update command: Update-package–reinstall < package name >

Ii. forcing a package to be unloaded (regardless of dependencies)

This is actually combined with the following to form "demote the specified package to the specified version." Because demotion is the first to unload a package, but because it is possible to be dependent on other packages that cannot be uninstalled, you can use the following command to force the uninstallation of a package without affecting other dependencies.

Forced Uninstall: Uninstall-package < package name >-force

Third, install the specified package version

The default is to install the latest version of the package through the graphical interface, but sometimes because of compatibility issues, you may not want the latest version of the package, you can use the following command to install the specified version of the package.

Install the specified version: Install-package < package name >–version < version number >

The version number can be obtained from the package on the NuGet page:/">http://www.nuget.org/packages/< Package name >/

As you work in the console, be aware of the items you are working on to avoid confusing problems:

MVC Scaffolding does not support the Entity Framework 6 or later as a few tips for NuGet