Setup project and detect dependencies

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Tim Anderson - 07 May 2004 08:15 GMT

I have a multi-project solution in VS 2003. It includes a setup project. Is
there any way to turn off "Detect dependencies"? Or to make it respect my
Exclude choices?

What happens is that Detect Dependencies detects the same assemblies
multiple times. Then the setup build warns that multiple targets have the
same name and location. So I mark the duplicates to be excluded. This works
for a session, but next time I open the setup the duplicates reappear.

Any suggestions?

Tim

Windows installer too complex?
http://www.itwriting.com/blog/?postid=41

Reply to this Message

Elizabeth Newman [MS] - 07 May 2004 20:43 GMT

Unfortunately, there's no direct way to turn off dependency analysis. However, there is a workaround: you can uncheck the "Include standard search paths" option in the
dialog that comes up from the SearchPath property. However, there are a few additional points to consider:
(1) You need to add your files using Add -> File. If you use Add -> Project Output then dependencies reported from the code project will be included.
(2) When you build, you may see one or more "Unable to find dependency" warnings, but these can be ignored in this case.
(3) If you only want to turn off dependency analysis for some files, then you can put those files in a merge module project with standard search paths turned off. Then use
Add -> Merge Module to include the .msm in a regular setup project with standard search paths turned on.

Hope this helps,
Elizabeth Newman
--------------------

>From: "Tim Anderson" <timjand@hotmail.com>
>Subject: Setup project and detect dependencies
[quoted text clipped - 26 lines]
>Windows installer too complex?
>http://www.itwriting.com/blog/?postid=41

----
Elizabeth Newman ? Visual Basic Deployment Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Tim Anderson - 07 May 2004 23:10 GMT

> Unfortunately, there's no direct way to turn off dependency analysis. However, there is a workaround:

Many thanks for your excellent suggestions.

Tim

Reply to this Message

Ken B - 18 Jan 2005 17:50 GMT

Why does the dependency checker not respect previous attempts to
exclude files. When I look at the setup project file it shows
exclude=true for the dependent file but the dependency checker
continues to add them to the package. The project is in source control
and therefore read only.

Reply to this Message

Setup project and detect dependencies

Free Magazines