CODEWITHSUNDEEP
c#visual-studio-2010dependency-propertiessolution
user1025852
user1025852

Reputation: 2784

one solution depends on another solution dlls

My solution builds another solution in a pre-build step - takes the artifacts to itself as a "deployment folder".

My references are at the dll level assuming the files are there.

The weird thing is that any new code I write in the first solution (for example change method name) is ignored by the the second solution that depends on the first.

I tried many things like clean solution, rebuild, disable the QTagent between tests and everything. seems like he remembers the first snapshot of the class and that's it - won't takle any changes when I try to debug.

What is the best way to work between solution so code can be called in that way?

Upvotes: 1

Views: 602

Answers (1)

Aidiakapi
Aidiakapi

Reputation: 6249

You should reference the original project (of solution 1) in your solution (2), then in the main project you add a reference to the referenced original project. Visual Studio takes care of the rest.

This looks like:
Example http://imageshack.us/a/img11/7493/57388651.png

If you're using it to run tests, then you can add the test project to the original solution. With the default Visual Studio Unit testing this'd look like:
Example 2 http://imageshack.us/a/img39/3590/25226157.png

Upvotes: 1

Related Questions