anchor.diff:  and a third time to install the resulting library into the client installation directory
   tree:
   
  -    <code>
  -    \> cmake c:\nc\templates\security -DGEODE=c:\nc<br />
  +    When building for Windows, specify the code generator (usually "Visual Studio 12 2013 Win64") in the configuration
  +    step and the config type ("Debug" or "Release") in any build steps:
  +
  +    <code>
  +    \> cmake -G "Visual Studio 12 2013 Win64" c:\\<i>gc-dir</i>\templates\security -DGEODE=c:\_gc-dir_<br />
       ... creates a makefile and other supporting files<br />
  -    \> cmake --build .<br />
  +    \> cmake --build . --config Release<br />
       ... builds  securityImpl plug-in<br />
  -    \> cmake --build . --target install<br />
  +    \> cmake --build . --config Release --target install<br />
       ... installs securityImpl in the client installation directory tree ($GEODE)
       </code>
   
  
positive.code: 
  8. Run `cmake` twice, once to configure the build, then again to build the examples, specifying the
  path to the `cmake` instructions located in the quickstart example directory (in this case, we're building the the `csharp` examples):
  
      <code>
      \> cmake %GEODE%\SampleCode\quickstart\csharp<br />
      ... creates a makefile and other supporting files<br />
      \> cmake --build .<br />
      ... builds the examples
      </code>
  
  
negative.code: tree:
  
      <code>
      % cmake -DGEODE=_gc-dir_ -DCMAKE\_INSTALL\_PREFIX=/installation-destination _gc-dir_/templates/security <br />
      ... creates a makefile and other supporting files<br />
      % cmake --build .<br />
      ... builds  securityImpl plug-in<br />
  