Hello -
We are having trouble creating a setup program using a Visual Studio
2005 installer project:
In the setup's "file system" we have in one folder the "Primary output"
from another assembly. Let's call this PO.dll.
We do not wish for the dll's on which PO.dll is dependent to be copied
to the same folder as PO.dll. We therefore selected the project for PO
and set the "copy to local" property on each reference to "false".
We then opened the setup project and set the "exclude" property for
each dll listed in the file system view to "true".
This appears to get rid of the dependencies. We can build, AND check
the project in without any changes taking place.
However, when we re-open this project, the detected dependencies
are re-generated and PO.dll once again show up in the same output
folder as PO.dll.
How can we stop this from happening? Any help would be greatly appreciated.
thank you.
ED
|
| emccormi Friday, August 11, 2006 4:53 PM |
Hi,
have you found a workaround? I have the same problem
|
| Nona686688 Saturday, August 19, 2006 2:25 PM |
I have this problem too. |
| matheny Tuesday, October 17, 2006 12:43 PM |
I have Visual Studio SP1 installed and also am experiencing this problem. I also have seen duplicate dependency Dlls listed in the Detected Dependencies list as well (and both are listed as NOT Excluded, when the project was last saved and checked in with the DLL set as Exclude = True). Has anybody determined a workaround? |
| Dan Dittenhafer Tuesday, August 07, 2007 2:55 PM |
Quick Update: It appears this issue only applies to the first DLL (alphabetically) in the Detected Depenencies list. My other excluded binaries continue to be excluded. I have a total of 19 DLLs in the DD list, numbers 2-18 seem to keep their Exclude = True setting from session to session. |
| Dan Dittenhafer Tuesday, August 07, 2007 5:06 PM |
Hi,
Are anybody have found solution for this problem?Are any patches from MS exists to solve it?This bug is still reproduces with VS 20058.0.50727.762 (SP.050727-7600)It is really annoying to exclude dependences before every rebuild  |
| Alex Nechiporenko Tuesday, November 27, 2007 11:06 AM |
I am also having this problem, using the same VS 2005 SP as Alex. For me,none of myDetected Dependencies exclusions show up until I do a build. If the .vdproj file is write-protected (e.g. checked intoClearCase), the previous exclusions made are preserved after the build. If the .vdproj file is writable (e.g. checked out from ClearCase), the exclusions are erased after the build. Any suggestions or identification of a patch that fixes this would be appreciated! |
| jkcraig Thursday, November 29, 2007 9:16 PM |
Hi,
After moving to .NET 2.0 (Visual Studio 2005) I have the same problems:
1) Duplicate assemblies in the "detected dependencies" list.
2) Exclude property's changes can not be saved.
Do you have any progress on this problem? |
| Alexey Kruglov Wednesday, January 23, 2008 3:54 PM |
Same problem with Visual Studio 2005:
1. Several projects in the solution have a dependency on the same file (A.dll). A.dll exists in two different directories (C:\Product1\A.dll and C:\Product2\A.dll). Some projects have a dependency on C:\Product1\A.dll and others on C:\Product2\A.dll.
2. The deployment project detects 2 dependencies on A.dll. Both must be excluded because A.dll is installed by another product. Therefore we exclude both detected dependencies on A.dll from the Detected Dependencies folder.
3. The change saves fine. However, each time the solution is reopened, the excludeflag on both files is reset -- i.e. A.dll is not excluded. Both instances of A.dll have to be excluded manually before each build.
This thread has been active for 1 1/2 year without any feedback on this bug. Can we finally get a moderator from Microsoft to reproduce this problem and provide some suggestions? - Proposed As Answer byJohannes F. De Rek Tuesday, August 18, 2009 12:29 PM
-
|
| Erwan H Wednesday, March 05, 2008 5:44 PM |
Re:
"This thread has been active for 1 1/2 year without any feedback on this bug. Can we finally get a moderator from Microsoft to reproduce this problem and provide some suggestions?"
Well, it's > 2 years now, so I'm thinking probably not. |
| omegaomega Wednesday, September 03, 2008 7:51 PM |
I'm having the same problem. Don't know if this happens in VS2008, but it would be nice to have some kind of fix or workaround from Microsoft.
I've rechecked and it don't seem to be any mistake we're doing...
|
| nelsonfsr Thursday, September 25, 2008 1:31 PM |
Yes, it is also happening in VS2008, it is driving me crazy, I've wasted many hours trying to resolve the problem and I cannot use automated build unless it is fixed. Is there any help at all from MS available on this problem? |
| dpmartin990 Monday, October 13, 2008 9:20 PM |
I found another thread (in this forum)with a posting of a possible workaround. I haven't tried it yet, but figured I'd go ahead and link these threads. If anyone tries it (or has found another solution/workaround) please post.
"Exclude property of dependent files does not persist within .vdproj"
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1147130&SiteID=1
|
| emc3 Friday, November 07, 2008 5:58 PM |
Thanks for the link emc3! Good idea by DavidR100 to use a merge module as a workaround. I haven't yet tried it myself, but it definitely sounds feasible.
- Proposed As Answer byJohannes F. De Rek Tuesday, August 18, 2009 12:28 PM
-
|
| Dan Dittenhafer Friday, November 07, 2008 6:21 PM |
I have a VS2008 solution with a number of DLL projects in it, and I also got duplicates in my install project. The problem is that some of the projects cross reference DLLs created by other projects in the solution and during the compile the cross-referenced DLLs are copied to the output directory of the project being built. (i.e. you land up with a directory containing the DLL from the project together with some of the DLLs that it references)
I managed to get rid of the duplicates in the install project by forcing the output of every project to go to a common directory. By default every project will send its output to the "/bin/Release" directory. Forcing this to go to a common output directory (e.g. "../Bin/Release" or "C:\Foo\Release" for every project) prevents the duplicates.
This is a nasty kludge but it worked for me. It looks as if the thing that checks for dependencies in an installer package is not clever enough to determine that the cross-referenced DLLs from a solution are scattered all over and that it only needs to include one copy.
PS. If one (or more) of the DLLs that are output from a project in your solution is shown in the "Detected Dependencies" you must remove the "Primary Output from xxxx" otherwise you'll still get duplicates.
|
| Johannes F. De Rek Tuesday, August 18, 2009 12:50 PM |
Funny coincidence... This thread has been dormant for half a year save for the above post,and here I am searching for a patch or workaround for the "mysterious detected dependencies appear" problem with Google dropping me here a mere 5 hours after it's resurrected.
I guess given the history aboveit's probably too much to hope for that the mostly brain-dead mini installer project could be improved as a patch to Visual Studio 2008. Here's hoping for an improvemenet in Visual Studio 2010!
-Noel |
| Noel Carboni Tuesday, August 18, 2009 6:26 PM |
index > ClickOnce and Setup & Deployment Projects > Exclude Filters Overwritten on Detected Dependencies when Re-Opening Project