anchor.diff:  
   === Run a Successful Build
   
  -Within this *build.xml* file is a target called *build*. This will build the NSF that should not have any problems.
  -This target is listed as the default target in the root element of the build.xml file (not shown here).
  +There is also a target called *build*. This will build the NSF.
  +This target is also listed as the default target in the root element of the build.xml file.
   
   This target makes use of the *bxp:buildnsf* task which will connect to the Headless Designer Plugin, and instruct it to build the nsf as specified by the task attributes.
   
  
positive.code: The files for this Demonstration are in the *demo/buildnsf* folder of the Build4XPages distribution files. The sample On-Disk Project is located within the tutorial folder as *sampleodp*. 
  The Application has a Custom Control and an XPage which uses that custom control.
  
  === build.xml
  
  Our 'recipe' for the build is contained in the *build.xml* file located in the *demo/buildnsf* directory. *build.xml* is the default name for an Ant build file, you can call it another filename but if so you would need to specify extra command line argument `-b myfile.xml`
  
  Within the build.xml file are things called _targets_. A target is a bit like a code block.
  Targets can be configured to depend on another target, so that means executing a _target_ will cause the other targets that it depends on to be executed first.
  
  Within this build.xml file are 2 _targets_ that are used to setup the demo *clean* and *init*
  
  *clean* is used to clean up any previous attempt at this tutorial, and *init* is used to initialise a new attempt.
  
  
negative.code: Total time: 2 seconds
  ----
  
  Also, in your domino Designer workspace you should see a new NSF with filepath *temp\BuildXPagesDemo.nsf*
  
  ==== Example of an NSF Build with Errors
  
  Let's see an example of running an NSF Build that results in some errors. To do this we will use the same sample On-Disk Project, but before we run the build we will sneakily delete the custom controls.
  This should cause an error when Designer tries to build the XPages that use those missing custom controls.
  