If you want to get some limited Intellisense when you’re editing or creating NaNT .build files then you can try the following:

  1. Copy the nant.xsd file from inside your NaNt schema directory.
  2. Paste it into your Visual Studio XML Schemas directory (e.g. C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas\
  3. Restart Visual Studio

When you next load up an existing .build file, Visual Studio should detect it correctly as an XML document. To get the Intellisense to work, you will need to add the XML Namespace to the <project> tag. Start typing the additional attribute ‘xmlns=’ within the opening <project> tag and Visual Studio should offer you the following auto-complete option:

xmlns=http://nant.sf.net/release/0.85/nant.xsd

So your full project tag should look something like :

<project xmlns="http://nant.sf.net/release/0.85/nant.xsd"
name="Your Build Name"
default="all"
basedir=".">

For new .build files, you can select the Schema you want to base your new XML document on by browsing in the Schemas box in the Properties window. You should find xml\Schemas expanded and the nant.xsd entry able to be selected. Tick the nant.xsd box.

Tagged with:
 

4 Responses to NaNT .build file Intellisense

  1. Andrew Gunn says:

    If you include other external build files, they too must reference the same namespace (as pointed by Jonathan himself).

  2. Nam Gi VU says:

    I have a question: How can Visual Studio automatically recognize that the xml schema associated with an existing .build file is nant.xsd?

  3. [...] to 3) Jean-Paul S. Boodhoo’s Blog – NAnt Starter Series (a detailed tutorial) and 4) NaNT .build file Intellisense (a cool Visual Studio intellisense feature). 10.759180 [...]

  4. Uday Kumar B R says:

    Nice one :-)

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>