Hi Scott,

The following is an example of a build that I perform: 


<!-- Core infrastructure components -->
<target name="level1">
        <csc target="library" output="Core.dll">
                <sources>
                        <includes name="*.cs"/>
                </sources>
        </csc>
        ... other base level components
</target>
<!-- Business Objects -->
<target name="level2" depends="level1">
        <csc target="library" output="customer.dll">
                <sources>
                        <includes name="*.cs"/>
                </sources>
        </csc>
</target>
<!-- Web Services -->
<target name="level3" depends="level2">
        <csc target="library" output="customerWS.dll">
                <sources>
                        <includes name="*.cs"/>
                </sources>
        </csc>
</target>
<!-- Web Pages -->
<target name="level4" depends="level3">
        <csc target="library" output="businessportal.dll">
                <sources>
                        <includes name="*.cs"/>
                </sources>
        </csc>
</target>

In this example I have a core.dll, customer.dll, customerWS.dll and a
businessportal.dll.  If something in businessportal.dll changes then as far
as I know a complete build needs to be performed.  However in theory only
the businessportal.dll should need to be recompiled.  This means that the
entire site has to be recompiled (because I am using strong names) and more
importantly redeployed.  The scale of the problem becomes a lot larger when
you have deployments over multiple machines.  Then the deployment scenario
for a small change becomes a lot more horrendous.  
Down time is a critical factor in our business and if we don't achieve a
certain level of uptime then we violate or contractual obligations.  It
would be good to hear from some other people to see whether they are
experiencing the same types of problems.  

Thanks
Ben


-----Original Message-----
From: Scott Hernandez [mailto:[EMAIL PROTECTED]]
Sent: Friday, 17 January 2003 7:15 PM
To: Ben Singh; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Building and deploying applications with Nant


Can you send us an example of a real-world data centre situation where you
need to do dependency related stuff.

I've been thinking about adding a <uptodate> conditional task. It would
allow you to only do certain things if something was not up to date.

Kinda like this:

<uptodate sourcefile="test.cs" updatedfile="test.dll">
    ... stuff to do
    <call target="build"/>
</uptodate>

It would probably work very similar, but a little simpler than the ant
uptodate task. http://jakarta.apache.org/ant/manual/CoreTasks/uptodate.html

----- Original Message -----
From: "Ben Singh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 16, 2003 9:20 PM
Subject: [nant-dev] Building and deploying applications with Nant


> > Hi,
> >
> > I was wondering whether I could get some feedback about the scenarios
> > people are using Nant for.  The current scenario I am faced with is a
data
> > centre operation with high availability requirements.  My problem is
that
> > making even minor changes requires a full build with Nant and
subsequently
> > a full deployment which results in down time.  Surely there has to be a
> > better way.  My previous posting on how to create a patch went
unanswered.
> > I suspect this is a very difficult question to answer and that Nant is
> > probably not designed to handle what I think is a pretty common
scenario.
> > If I'm totally wrong someone please shoot me down.
> >
> > Ben
> >
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: Thawte.com
> Understand how to protect your customers personal information by
implementing
> SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
> Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
> _______________________________________________
> Nant-developers mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to