Initial roughing out of some profiling context

wcat binaries (http://www.iis.net/community/default.aspx?tabid=34&g=6&i=1466)
Orchard.Profiling project to hold some wcat scripts for generating stress-style load and specflow features for generating fixed sets of requests
"add profiling data" command in Orchard.DevTools to create a number of samples page and blog content items
"build.cmd profiling" target creates build\Profiling web dir from clean build, and execs baseline setup and population via orchard cmdline

--HG--
branch : dev

lib/wcat/doc/readme.txt

@@ -0,0 +1,37 @@
+Getting Started with WCAT
+======================================
+
+Documentation
+    It is suggested that you read the documentation for WCAT in order to understand
+    the environment and configuration needed.  Documentation can be found under the
+    doc folder in the directory that you installed WCAT to.
+
+Installing WCAT
+    Prerequisite: all machines that will run WCAT must have the administrator account
+    enabled and must all share a common password.
+
+    1.  Log into the WCAT Controller as administrator.
+    2.  Install wcat.msi on the machine to be used as a WCAT Controller.
+    3.  If any WCAT extension DLLs will be used, copy them to the WCAT installation
+        directory. (typically c:\Program Files\WCAT)
+    4.  Open a command prompt; navigate to the WCAT installation directory.
+    5.  Run <20>cscript //H:Cscript<70>
+    6.  Run <20>wcat.wsf <20>terminate <20>update <20>clients {comma separated list of WCAT client
+        machines}<7D> where the <20>clients<74> parameter accepts a comma separated list (no
+        spaces) of the machines you plan on using as WCAT Client machines.  Note: If
+        the WCAT Controller machine will also be used as a WCAT Client, include
+        <20>localhost<73> OR the name of the WCAT Controller machine in the list of clients.
+
+        NOTE: If WCAT has never been installed on the WCAT Client machines before,
+        this will cause the machines to reboot.
+
+Running WCAT
+    1.  Log into the WCAT Controller as administrator.
+    2.  Install wcat.msi on the machine to be used as a WCAT Controller.
+    3.  Open a command prompt, navigate to the WCAT installation directory (typically
+        c:\Program Files\WCAT)
+    4.  Run <20>wcat.wsf <20>terminate <20>run <20>clients {comma separated client list} <20>t
+        {scenario file} <20>f {settings file} <20>s {name of the Web Server} <20>singleip -x
+    5.  Output will be generated in the current directory, <20>log.xml<6D>.  To change this,
+        use the <20>-o<> flag.  For more help on options to pass to wcat.wsf type
+        <20>wcctl.exe -?<3F>