Visual Studio Project Dependencies

I have a Visual Studio.Net Solution that has many projects / libraries.

When I work locally on my own computer, there is no problem, as I tend to recompile the libraries that I just changed, and everything is synchronized.

The problem is that sometimes developers who need to work from time to time or look at my code have a huge problem recompiling everything.

In the configuration manager, I do not have all the tested projects, it will take too much time to create everything that works.

The problem is when the solution is compiled in another application, some of the errors reported say that a particular library has an error, and it takes too much time to figure out all the dependencies that make up each of them separately.

Even when checking everything in the configuration manager, it still does not compile correctly.

I thought when you add a link to a library that dependencies care about.

Is there an easy way to make sure the solution determines what the correct dependencies are, and make sure everything is built in the correct order?

thanks

+2
visual-studio dependencies project
source share
2 answers

After other developers have received new source codes from you, they should close Visual Studio and reopen the solution.

Visual Studio sometimes has dependency problems. First try the following menu commands:

Build > Clean Solution Build > Rebuild Solution 

This will show you which dependencies are circular or incorrect. In addition, the Visual Studio project should not depend on another that creates the executable file (at least for our pure C ++ script, this is true). That is, the Utils project, which compiles to Utils.dll, cannot depend on the MyApp project, which exports some functions or characters and compiles as MyApp.exe and MyApp.lib (or some other kind of installation ) If you have such a dependency, you must correctly configure the construction order of the project and manually install MyApp.lib as in the linker attachments.

+2
source share

You can package and distribute your builds using http://nuget.codeplex.com/ . He decided to solve this problem.

+1
source share

All Articles