.Net Deployment Project Detected Dependencies magically un-excluded

Question

I have a Visual Studio 2005.NET solution that has 20+ subprojects, including a deployment project. The VS2005.NET deployment project has a number of dependencies discovered that were manually excluded and the values ​​added manually were corrected.

Sometimes, however, these detected dependencies become magically not excluded, which causes a warning in the assembly: WARNING. Two or more objects have the same target location ('[targetdir] \')

What is a trigger that causes a detected dependency not to be ruled out? Can deployment solutions alert them to errors so that the nightly build does not continue?

Answer 1

I had the same problem and considered it for about a year before giving up and switching to WiX . It also did not help me "double" my builds, because MSBuild for VS2005 will not work with deployment projects.

In any case, you might want to consider something like WiX for your installations.

Answer 2

This happens when the dependent project has "Copy Local" installed on the dependent DLL. The deployment / installation project has both a source and a copy of the DLL specified as a dependency.

Answer 3

, , - :)

2 :

a) DLL

b) DLL - .

, reset , .

:

a)

b) DefaultLocation , , , DLL . .. ASP.NET [TARGETDIR]\bin

c) DLL , .

What is it. You should not receive any warnings for these DLLs, if you have additional features, just drag them to this folder.

Hope this helps.

-Konstantinos

Answer 4

A discussion of detected dependency detection here may explain the behavior if you use multiple development environments with the same project:

http://www.xmission.com/~legalize/msi/known-bugs-2003.html