One or more packages could not be completely uninstalled

前端 未结 9 1427
栀梦
栀梦 2021-02-06 20:44

I have an ASP.NET MVC 4 application. I used NuGet to update all of the NuGet packages that were installed when I created the application. One of the packages was Microsoft.B

相关标签:
9条回答
  • 2021-02-06 21:21

    I believe this problem is caused by the packages being read-only or otherwise inaccessible at the file system level.

    Packages under source control

    Temporary work-around (untested)

    Check out the entire packages folder prior to telling NuGet to restart Visual Studio to delete the packages.

    Permanent work-around

    I found that this could be permanently resolved by removing the packages from source control and instead using NuGet Package Restore.

    Packages not under source control

    Temporary Work-Around

    I worked around this by deleting from the solution's packages folder all of the files that referenced the package in question. Specifically, these were:

    1. Folder: Microsoft.Bcl.Build.1.0.7
    2. File: Microsoft.Bcl.Build.1.0.7.deleteme
    0 讨论(0)
  • 2021-02-06 21:22

    I'll agree that this can happen when your packages folder is under source control. If you like to have it there, instead of removing the bindings you can check it all out, remove the package with the NuGet Package Manager, and then check in after wards.

    0 讨论(0)
  • 2021-02-06 21:24

    If you are using Entity Framework 6, then you can install the NuGet package "EntityFramework.SqlServerCompact".

    This enabled me to use the standard ASP.NET Identity tooling that comes with the project templates for 2013 and MVC5.

    0 讨论(0)
提交回复
热议问题