Hearn, Bruce wrote:
One obvious consideration for going to NANT is how to manage your projectThis 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.
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 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
