This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
System.IO.DirectoryNotFoundException: Could not find a part of the path \packages\Microsoft.Extensions.DependencyInjection.Abstractions.8.0.0\buildTransitive/net461/Microsoft.Extensions.DependencyInjection.Abstractions.targets
Shouldn't the installer take care of creating the targets of the dependencies for the package?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hello @Nieman, Michelle J,
I agree with @Michael Taylor, if you try to put the solution/project into a short directory, will this error disappear?
Besides, I am thinking if there’s any limitation on your machine, like permission limitation. Will running VS as administrator work?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Yes it will. That isn't the issue here I believe. One thought that comes to mind is that your project is in a long directory and adding all this extra pathing is causing it to exceed the max path size.
Another thought is that there was an issue with downloading the package. Since you are targeting NET 4.6 it looks like then check your packages folder to confirm it was downloaded. If not then restore the packages again.
Yet another thought is that your upgrading and there is a conflict between the old and new packages. Close VS, wipe the packages folder and open VS back up and restore the packages again. Then try upgrading.
It ended up being that my paths were too long. Thanks for the help!