When vs2012 installs automapper under. Net 4.0, the following error will be reported:
‘automapper’ already has a dependency defined for ‘standard. Library’.
‘AutoMapper’ already has a dependency defined for ‘Standard.Library’.
It is found that the nuget Version (version 2.83 of vs2012) is lower, and the standard. Library framework is not supported.
There are two solutions
Method 1
nuget 2.12 supports the. Net standard framework used by automapper 5.0.1 nuget package, so nuget needs to be upgraded to nuget 2.12 or above
PM & gt; Install-Package AutoMapper -Version 4.1.1
Installing ‘AutoMapper 4.1.1’.
Successfully installed ‘AutoMapper 4.1.1’.
reference resources:
http://majing.io/questions/557
Reproduced in: https://www.cnblogs.com/yanglang/p/7065049.html
Read More:
- Vs2019 nuget configuring OpenGL
- Solution to the problem of unable to open glaux. H in vs2013
- Solution to unknown internal error in StarUML installation extension
- Solution to the problem of console flash in vs2017 runtime
- Solution to the problem that OpenGL can’t find glew32.dll in vs2019
- Solution of unable to open source file “StdAfx. H” in vs2013 / 2012
- The solution of configuring OpenGL in vs2017
- Solution to the error of ODBC driver in windows installation of Postgres database
- In vs2013, reshharper and team management plug-in git share a temporary solution to the “failed modify to document” error.
- Solution to the problem of vs2017 error report unable to open source file
- Solution of node canvas error reporting in MacOS M1 installation
- An error occurred when installing vs2017: failed to verify the signature of the installation program list
- Solution — windows 2012 installation Framework 3.5 in VMWare
- Solution of error reporting in PIP installation of iPhone
- Solution: how to set program permission as administrator permission in vs2019
- Internal error 2503 solution in endnote installation
- VTK + QT + vs compilation and installation configuration
- Unable to install SQL Server (setup.exe), VS Shell installation has failed with exit code 1638.
- Solution to node sass installation failure
- The perfect solution of VS2010 console program running in a flash