All geek questions in one place

My team member added a link to a third-party DLL and registered ... now I can’t build

My team member made a link to the DLL on his local disk (for example C:\mystuff\thirdparty.dll) and checked the link in the project. I've updated your local copy of the project, and now I have a broken link: <The system cannot find the reference specified>. I have thirdparty.dll on my local machine, but this is not in the same directory as my team member.

Should we check the source control under our solution in the thirdparty.dll file in a subdirectory using the relative path? When another developer receives the project, he will pull out the DLL and automatically execute , even if the developer did not "install" the DLL in advance?

Thanks.

+3
source share
3 answers

If you create the "lib" or "assemblylies" directory as part of the solution, or at least in the version control project, and add all the assemblies of 3d batches and reference them there, it should fix many problems like yours.

Generally, you will not need to use the 3d party installer, but this will depend on the product.

+8
source

From my experience, the best way is to set the relative path to the specified DLL in the public folder. For example, given the following structure:

  • Big project
    • Project 1
    • Project 2
    • ...
    • Project N
    • Bin

I have all my projects compiled to the bin folder, and all projects reference their dependencies from the bin folder. Anyone can bring the project to ANY location and compile it for the first time.

+1
source

Source: https://habr.com/ru/post/1705100/

More articles:


All Articles