You should be able to use the msi mergemodule element and just let it sort things out. The moduledependencies element just "strongly forces" the dependency to another merge module. Out of curiosity, why not just create one merge module containing all dll/ocx files? That is just asuming that you have one install and all of those files end up in that one install.
I'll note the "request" to just reference the merge module by itself (for moduledependencies). I should be able to open up the target merge module and retrieve the necessary information... Jim > Jim, > As a matter of fact, I built the documentation yesterday and saw that > it > had been changed :-) > > So if I understand correctly, I cannot simply add a dependency to a > merge > module by referencing the msm file itself, I need to use the > moduledependencies tag and give it the proper name.id attribute? Ok, I > think I can handle that :-) > > What I'm trying to do is to create merge modules for a couple dozen > dll/ocx files by having a program create the .build files for each one. > I was hoping I could use the msi task mergemodule tags which seem to > let you specify a path to a msm file and let it figure everything else > out. I suppose I'll have to have my program that is creating the msm > .build files create the correct moduledependecies tag. > > I'll try and get that working today. > > Thanks again for your help. > > John Cole > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, April 02, 2004 8:24 AM > To: John Cole > Cc: [EMAIL PROTECTED] > Subject: Re: FW: [NAntC-Dev] Example for creating a simple msm file? > > > So, to add a dependency for merge modules, you should add the > <moduledependencies> tag to the merge module xml fragment. > > I just added some documentation to the install tasks (two nights ago), > but unfortunately the nightly build docs haven't been generated with > this new information. In that documentation (for the msm task), I > described the moduledependencies element and the sub-element(s) for it. > It might be worth grabbing the latest from CVS and generating the > documents yourself. That way you can view the help docs for msi/msm > tasks... > > Basically you'll want to add an element similar to this for the B > module fragment. Note, the id attribute should equal the id of the > dependent merge module (A). > > <moduledependencies> > <dependency id="MergeModule.A.2D74BC37-7F9F-4DFA-B9D4-E048F74CCE2D" > language="0" /> > </moduledependencies> > > Then you would add both merge modules to the msi install. For more > information about module dependencies, check out the page about them: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/m> > oduledependency_table.asp > If you need further information, please don't hesitate to ask. > > Jim > > >> -----Original Message----- >> From: John Cole [mailto:[EMAIL PROTECTED] >> Sent: Thursday, April 01, 2004 1:52 PM >> To: 'James Geurts' >> Subject: RE: [NAntC-Dev] Example for creating a simple msm file? >> >> Jim, >> Thanks very much! Your NAnt version worked! I'll keep trying to get >> the >> cvs version working, but I have yours in case it doesn't. >> >> Now another msm question :-) I have created a msm file from your >> example. >> If I wanted to add a msm as a dependency to the example, how would I >> do that? >> >> For example if I create a msm for a.dll and then need to create a msm >> for >> a.dll, but b.dll depends on a.dll, how do I make the b.msm include >> a.msm? >> >> Thanks again for your help. >> >> John Cole >> > > > > ------------------------------------- > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. This message contains confidential information and > is intended only for the individual named. If you are not the named > addressee you should not disseminate, distribute or copy this e-mail. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
