The only workaround for us was to clone the solution from the remote repository to a fresh local directory.
We tried emptying the NuGet cache, but without success. The problem is that the .dll-File was not present in the package directory (see file path from OP). Mixed backward and forward slashes are not a problem. Deleting/restoring packages did not solve the issue. Commands like Get-Package didn’t work either.
We tried diffing the two folders, a) the freshly cloned working one and b) the old not working one, as we suspected that config files not under version control caused the issue. But without any success. We couldn’t find any relevant difference. The binary .suo-File was not considered by us. Deleting the .suo-File and restoring packages didn’t solve the issue either.
We gave up on that point because we have a workaround to deal with this issue.
I would dig for global VS/NuGet cache/setting files but we decided to not invest more time on that.
3
Answers
By referencing these Nuget Official Site and .Net Standard Implementation Support Chart, .Net 4.6.1 is compatible with NetStandard2.0 Applications.
Please check the version compatibility from the above references and try installing the required dependencies.
The only workaround for us was to clone the solution from the remote repository to a fresh local directory.
We tried emptying the
NuGet
cache, but without success. The problem is that the.dll
-File was not present in the package directory (see file path from OP). Mixed backward and forward slashes are not a problem. Deleting/restoring packages did not solve the issue. Commands likeGet-Package
didn’t work either.We tried diffing the two folders, a) the freshly cloned working one and b) the old not working one, as we suspected that config files not under version control caused the issue. But without any success. We couldn’t find any relevant difference. The binary .suo-File was not considered by us. Deleting the .suo-File and restoring packages didn’t solve the issue either.
We gave up on that point because we have a workaround to deal with this issue.
I would dig for global VS/NuGet cache/setting files but we decided to not invest more time on that.
I had the same issue and as you wrote that copying repository to fresh local directory worked for you, I made some tests.
I have figured it out, that the problem is windows’s path lengt limitation to 260 characters.
Maximum Path Length Limitation