|
Stephen Boom mentioned that I missed the
NDoc.xslt include. This was just a result of my very half-a** attempt at
cleaning the VS.Net Project to NAnt build.xslt. It just includes your
NDoc task content. From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Cromwell It appears that SF.Net is blocking
zip attachments. Sorry for the size of the email. I've done some work with the template Ian mentioned below and made a
pretty powerful build environment out of it. There are some expectations
on your repository, but you can work around that. Here are a couple of
the requirements: 1)
Root relative paths. All Net
assemblies follow this directory structure standard: <Root> <Fully Qualified
Project Name (ie MyCompany.MyProject.Web)>
<Branch (ie 1.0, 2.0)>
<FQPN.xxproj> 2)
Two types of references: static
and project. Project references are only used when the scope of the
development effort spans multiple assemblies/projects. Static references refere to a specific build that has
been marked production ready. Attached is the xslt that we use against all projects. We have a
project.build file that iterates a list of VSS .xxproj paths to be built, gets
the latest version of the code and generates the project specific build (like
CCNet does). To configure a new project for the build environment we have
only have to add a single line to this project list. Common.build and
SystemInfo.build have some stuff that is less likely to change.
Common.build will be removed when NAnt Expressions make it to production. There are a few things that are currently disabled. COM+
references haven’t been tested using this XSLT, though they
shouldn’t require much work. Also, there is a logistical issue with
maintaining multiple branches at a time. We won’t run into this
wall as we are not a IT specific company, but an IT department supporting a retail
company (no product lines). The xslt is a very nice way to maintain dynamic builds, but the xslt
code itself is a disaster to read and maintain. I plan to start breaking
a lot of things out.
-----Original Message----- Evan, depends on what you are using as a source document. You can find an
xslt stylesheet to transform vs.net vcproj files here: http://radio.weblogs.com/0106046/VSConvert.xsl You might find that useful even if your input source is somthing
different. Ian Bonnett, Evan A wrote: >>From what I have read, this sounds like the most flexible
method to >auto-generate build files. Can someone explain how this works
and possibly >send a template file or sample? > >Thanks, > >Evan A. Bonnett >Reynolds and Reynolds, IT > > > -- Ian MacLean, Developer, ActiveState, a division of Sophos http://www.ActiveState.com ------------------------------------------------------- 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 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users |
NDoc.xslt
Description: Binary data
