Hi!

At the time that I'mbuilding my Setup Proyect I have a 8 warnings saying Two or more objects have the same target location?? and one error saying Unrecoverable build error??

I don't know what to do beacuse I can not find the error. Please help me if you have seen something like this before because I want to run my application in another computer....

Regards!!!

I had that problem...

Dependancies of my project output had dependancies themselves; and the setup project will recurse until it has all related dependancies... however, when these recursed dependancies conflict dosen't do anything about it.

So, the solution is to simply add in the references to all possible projects (or assemblies) which may get automatically included to the projects being added to the setup project.

Hope this helps!

Can you post the actual build messages?

Can you confirm that this is on VS2005?

Let's start with the "Two or more objects..." error messages. When those go away, we can look at the unrecoverable build error.

Basically, that error is saying that your setup is authored so there are files in the same folder with the same name. Usually, you can double-click on the error message and it will take you to one of them.

One way that can happen is if you add Project Output Groups from multiple projects that have the same dependencies. You can get multiple copies of the dependencies that way. If you go to the folder that has the multiple files, you should be able to select a copy and exclude them... or try the detected dependencies folder.

Some ways you can track this down would be to select an assembly and go to the property grid and open teh "dependencies" object. This way you can see which dependencies an assembly is bringing in. You can also go to a Project Output Group and check the "dependencies" properties or the "outputs" property, which lists the files in the project output group.

Really, once you figure out why you have multiple files of the same name in the same folder, we can find the best way to clean it up.

Good luck, hope this helps.

I had that problem...

Dependancies of my project output had dependancies themselves; and the setup project will recurse until it has all related dependancies... however, when these recursed dependancies conflict dosen't do anything about it.

So, the solution is to simply add in the references to all possible projects (or assemblies) which may get automatically included to the projects being added to the setup project.

Hope this helps!

Another way to handle that problem would be to exclude one copy of each dependency, so that only one is getting deployed.

Indeed. But personally, sometimes I find that this causes problems with custom actions if the files are depended on in that way.