Unfortunately it works only partially: my project already contains references to projects D.dll and C.dll - I need them to build custom action. When I include them as CustomActionContents, start the build and those dlls are not GACed yet - they are getting included twice in the command line of the packaging tool - and that fails the build: EXEC : error : An item with the same key has already been added.
Do you know if there is a workaround for this problem? The easiest fix for it would be to ignore that error and use the first instance of the item only. It would be nice if process that generates that command line, would always include outcome of ProjectReferences instead of eliminating GAC contents. That way you could in fairly intuitive way adjust what is added and what is not to the package: if you do not want something included, you put it as Reference, and if you want something you put is as ProjectReference, and if you want something that you do not have project for, include it as CustomActionContents. -----Original Message----- From: Jason Ginchereau [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 3:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] DTF Dependency Detection Hi Jacek, Sorry it's not documented yet, but I did design in a way define additional arbitrary files to be added to the CA package. You just need to put the file list in a property called CustomActionContents, by adding lines like this to your project file: <PropertyGroup> <CustomActionContents>dependency3.dll;path\to\resource.txt</CustomActionCont ents> </PropertyGroup> Let me know if that doesn't solve the problem. -Jason- -----Original Message----- From: Jacek Dudziak [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 1:25 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] DTF Dependency Detection Let me rephrase the question: is there a way to force MakeSfxCA to include some of the libraries that are in GAC? For example B.dll and C.dll are added to the CA project as references to their own projects vs references to .Net assemblies sitting in GAC. Could that force MakeSfxCA to include them into the Packaging phase? Is there any other way to do it? -------------------------------------------------- From: "Jacek Dudziak" <[EMAIL PROTECTED]> Sent: Tuesday, September 23, 2008 4:45 PM To: <wix-users@lists.sourceforge.net> Subject: [WiX-users] DTF Dependency Detection > I have a bunch of managed custom actions that rely on multiple DLLs. For > example CustomAction.dll is loading A.dll, A.dll is loading B.dll and > B.dll is loading C.dll. CustomAction.dll is registered as binary in the > MSI, but other dlls are registered as files. > > Some of those DLLs are also registered in the GAC. Let's say B.dll and > C.dll. > > I have added to my custom action project refereces to all projects which > create those DLLs. > > Whenever I build it on my machines everything works like a charm. But I > have couple machines where the same build process does not package B.dll > and C.dll (MakeSfxCA) - those that are getting registered in GAC. What is > worse it does not happen all the time - but quite frequently. > > Does anybody know why and how can I overcome it? Is it a bug in 3.0.4309.0 > build of Wix? What is the mechanizm for MakeSfcCA detect dependencies? Can > I influence it? > > Thanks > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
