> You can also set this by right-clicking on a .build file in a project > (add one to a project temporarily if you need to) and choosing Open > With... Choose "HTML/XML Editor" and click Set as Default.
File associations are cool, but the really neat trick is to get tag-completion for NAnt scripts in VS.NET! I'm much too lazy to look up syntax every time I need it. (Thank you, Bill, for ruining my short-term and short-term memories.) Copy a NAnt.xsd file that has the task schema in it into the following path (for VS.NET 2003): C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages\schemas\xml\ And then automagically any file with the correct schema definition at the top of the file will support tag completion in the VS.NET XML editor. (I prefer to give all my build files .build.xml extensions anyway.) <?xml version="1.0"?> <project name="eRealty.Desktop.ContractManager" default="build" xmlns="http://nant.sourceforge.net/";> [Which reminds me... The standard NAnt schema is incomplete, folks. My tag completion, particularly for nested elements, often fails me and I have to actually read the help file. Very upsetting. Heh.] There are other handy type-definition things that could be done to enhance the NAnt.xsd and provide more and better Intelisense... but I'm kind of swamped at the moment or I'd've already done it. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
