I am in charge of building a fairly large application containing about 250+ (grows daily) projects. I built my tools over a year ago - before I heard about NANT. It is split into 3 major parts: 1) Getting the projects from VSS 2) Creating a "build order" - figuring out all the dependencies, the project is not partitioned very well 3) building each project in order. I do this part by creating a nmake makefile from the .csproj file and some other inputs
I am currently building the build tools using nant and would like to extend what I've learned to our application get rid of the backend creation of makefiles and use NANT build files. Eventually replacing the whole thing with NANT. I thought I would have to write a tool to create NANT build files from the .csproj files similar to what I do now (parsing the .csproj file as xml) but it sounds like there is a xslt way of doing this. Slingshot is a start but xslt would be better. I have looked thru the documentation but can find nothing so I assume that the stylesheet is not part of the NANT distribution? Not being an xsl expert I would like to "steal" anything that would may my job easier :) Any pointers or help would be useful. One big advantage for me would be to get out of the "custom build tool" business. Currently I am the only one maintaining the build tools. Thanks, Tom Richards -----Original Message----- From: Gordon Weakliem [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 05, 2003 7:32 PM To: Hearn, Bruce Cc: [EMAIL PROTECTED] Subject: Re: [Nant-users] Advantages of NAnt Hearn, Bruce wrote: >One obvious consideration for going to NANT is how to manage your project >container artifacts (project files and solutions). It can be tedious to >manage both csproj and build files. To get around this, we use an xsl >transform to convert csproj to build files. But to do this, I have to use >msxsl.exe, because the <style> tag requires the source file to be >writable(!). > > This bug is fixed in the nightly builds, as best I can tell (at least I think I remember submitting a patch). Essentially the problem is that when the style task goes to open the input XML, it uses the default FileStream constructor, which asks for read access. You can patch the source for the StyleTask class pretty easily. You could also drive your build with a master build and use the <attrib> task to set the csproj readable before applying the style, I used to go to the extreme of checking the .build into source control until I realized that I could recreate it at any time from my stylesheet, so I quit that practice. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
