Sorry all, I got the address wrong the first time...
---------- Forwarded message ----------
From: Jim Geurts <[EMAIL PROTECTED]>
Date: Thu, 26 Aug 2004 08:30:22 -0500
Subject: Re: nant
To: "Burton, Kevin" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Whew... this is going to be a long answer, I fear :)
If your visual studio projects are merge modules, then you can merge
them with the msi generated by NAnt. If you would rather build a
merge module from NAnt, then you can merge that w/ the msi generated
by visual studio. For this example, I'll go with the first case:
So, for simplicity say you have webservice.msm and
ApplicationserverSetup.msi. This is a sample script that will merge
the webservice.msm with the ApplicationServer.msi
<msi
output="ApplicationServerSetup.msi"
sourcedir="."
banner="installlogo.bmp"
background="installbg.bmp"
license="license.rtf"
debug="true"
verbose="true"
>
<properties>
<property name="ProductName" value="Application Server" />
<property name="ProductVersion" value="1.0.0" />
<property name="Manufacturer" value="Sample"/>
<property name="ProductCode"
value="{2JKLASFC-EADS-420e-B6E5-E23ASDFSFFWE}" />
<property name="UpgradeCode"
value="{62F4F96C-E92B-420e-B6E5-E236C64A78AF}" />
</properties>
<directories>
<directory name="D__SAMPLE" foldername="Sample"
root="ProgramFilesFolder" />
</directories>
<components>
<component name="C__MainFiles"
id="{62F4F96C-E92B-420e-B6E5-E236C64A78AF}" attr="2"
directory="D__SAMPLE" feature="F__MainFiles">
<key file="MySample.txt" />
<fileset basedir="${samples.dir}">
<include name="*.*" />
</fileset>
</component>
</components>
<features>
<feature name="F__MainFiles" title="My samples main files"
display="1" typical="true" directory="D__SAMPLE">
<description>The core assemblies and executables.</description>
</feature>
<feature name="F__Webservice" title="Webservice" display="1"
typical="true" directory="D__SAMPLE">
<description>Installs the webservice</description>
</feature>
</features>
<mergemodules>
<merge feature="F__Webservice">
<modules>
<include name="webservice.msm" />
</modules>
</merge>
</mergemodules>
</msi>
So... with this snippet, the webservice is assigned it's own feature.
The feature is mapped to a directory (D__SAMPLE) so that the merge
module knows where to set TARGETDIR to. The main files (assigned to
the component C__MainFiles) for ApplicationServer are mapped to
another feature (F__MainFiles). Having multiple features allows the
user to specify which items they want installed (if they choose a
custom install).
Jim
On Wed, 25 Aug 2004 09:53:18 -0600, Burton, Kevin <[EMAIL PROTECTED]> wrote:
> I changed the sourcedir attribute to "." and added:
>
> <copy todir="${build.dir}">
> <fileset>
> <include name="ApplicationServerSetup.msi" />
> </fileset>
> </copy>
> <delete>
> <fileset>
> <include name="ApplicationServerSetup.msi" />
> </fileset>
> </delete>
>
> After the <msi> task and it works!!!
>
> Now some more questions. Up until now I have had two installations because I didn't
> see an easy way to merge the installations with Visual Studio. Now I think I can. I
> have one installation that installs the services and another that installs the web
> service. They were separate "projects" in Visual Studio. How can I "merge" the
> installation of the web service with this installation? I have a feeling that it has
> something to do with features but I don't totally understand what is going on with
> that token. Right now I have:
>
> <features>
> <feature name="DefaultFeature" title="DefaultFeature" display="1"
> typical="true" />
> </features>
>
> If I want to also install the web service with this msi file I am assuming that I
> will need to add another "feature" and/or change the existing one. I am not clear
> how this ties back to the list of components.
>
> Thanks again. I feel like I am really making progress.
>
> Kevin
> -----Original Message-----
> From: Jim Geurts [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 25, 2004 10:35 AM
> To: Burton, Kevin
> Subject: Re: nant
>
> Ok.. I'll try to help you out using this email address for now, I guess :)
>
> I seem to recall a problem putting quotes around the path. I'll look
> into maybe converting the path, passed to cabarc, to dos 8.3 format.
>
> A workaround for now is that you could copy the files to a temp
> directory and use that temp directory to populate the msi.
>
> Jim
>
> btw, I replied to your post on nant-users and nant-contrib-developers.
>
> On Wed, 25 Aug 2004 09:19:48 -0600, Burton, Kevin <[EMAIL PROTECTED]> wrote:
> > Thank you for your response.
> >
> > I guess somehow you were being blocked because this is the first email that I
> > received from you. I will try removing the space or somehow escaping it. Do you
> > think escaping the path or somehow enclosing it in quotes will work? It would be
> > very hard to change the directory path name for me at this point.
> >
> > Did you post to the NANT list or NANT-CONTRIB?
> >
> > Thanks again.
> >
> > Kevin
> >
> > -----Original Message-----
> > From: Jim Geurts [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 25, 2004 10:09 AM
> > To: Burton, Kevin
> > Subject: nant
> >
> > I don't know if your spam software blocks every email I send to you,
> > but I've answered your msi question 3 times now.
> >
> > Try removing the space from the directory path. I think there is a
> > bug w/ cabarc that does not allow file paths with spaces.
> >
> > Btw, I originally posted this, to the list & to your email, from
> > [EMAIL PROTECTED]
> >
> > Jim
> >
>
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NAntContrib-Developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
