I use Ultraedit (www.ultraedit.com) as my IDE for everything. Including NAnt.
It has user definable syntax highlighting. I had added build to the list of extensions that used the XML definition that ships with Ultraedit, but this was not ideal. Thanks to Jonathan for pointing me at the nantschema task, I have now written a "simple" buildfile that generates an ultraedit wordfile defintion for buildfiles tailored to *your* nant install. It could do with a little polishing up to use actual properties to override the hard-coded but easily over-ridable paths. And to specify which /L definition you are creating (it's totally hardcoded to /L12 at the moment as that's what I use). But it should be a fine starting point for anyone. End result is my buildfiles highlight up elements in a lovely way, so I can see which elements are real nant elements and which are type-o's etc. It uses an inline task (in a script block) to build the wordfile, and even with my custom generated wordfile, the wordfile task doesn't highlight, but, I don't expect many people use many tasks written in script blocks. Oh, it doesn't include functions, as they are not in the XSD. Anyway I can generate a list of them automagically? -- Michael Jervis [EMAIL PROTECTED] 504B03041400000008008F846431E3543A820800000006000000060000007765 62676F642B4F4D4ACF4F0100504B010214001400000008008F846431E3543A82 0800000006000000060000000000000000002000000000000000776562676F64 504B05060000000001000100340000002C0000000000
wordfile.build
Description: Binary data
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
