CODEWITHSUNDEEP
visual-studiotfsnugetnuget-package
Mr Bitmap
Mr Bitmap

Reputation: 231

TFS check-in error: Could not find a part of the path

Our team works on a project with TFS as source control. Sometimes that I want to check-in some errors happen.

D:\CustomManager.1.0.7184.35750\lib\net461\CustomManager.dll: Could not find a part of the path 'D:\CustomManager.1.0.7184.35750\lib\net461\CustomManager.dll'.

I gotta go to the Packages folder and make a new folder. after that, I have to copy the previous version of the package in that and then rename it to solve the case. This way is a little annoying because sometimes after that, new errors will show with different versions.

Additional information: This error will only be shown when I update the NuGet packages. Is there a simple way to fix this?

Upvotes: 1

Views: 1825

Answers (1)

PatrickLu-MSFT
PatrickLu-MSFT

Reputation: 51073

Seems you directly checked libraries(dlls) in to TFS and manage version control of them.

It's not a recommend way, there are multiple downsides such as it's never exactly clear which projects are using which versions of which assemblies. It's a maintenance nightmare.

Suggest you use Nuget to handle these libraries in TFS. You should compile your code, package it in Nuget and publish it. For multiple projects you can upgrade their nuget references when appropriate, or stick with the older versions if they need to. If you need to reference a known-good, stable version, you just make sure your project is configured to pull a specific version from NuGet.

TFS use Package Management that hosts NuGet, npm, and Maven packages alongside all your other TFS assets: source code, builds, releases, etc, also be able to handle the external packages.

You could add external packages to a TFS Package Management feed. When you restore the packages, select the feed. All need packages will be restored entirely. To achieve this, just use Push NuGet packages to specify the packages you want to publish and the target feed location.

More details please refer Get started with NuGet Package Management in TFS

Update:

Keep looking for old packages, this will not happen if you already referred the latest dll in project. Please double check this part.

In your situation, if you want to check the dll in source control, you should add dlls in the solution/project and use relative path. Otherwise, tfs server may not find path.

For cache issue, suggest you to clear TFS cache then restart VS, and check in again, this may do the trick.

Upvotes: 1

Related Questions