Calling SetVersion has the side-effect of locking our custom msbuild
tasks assembly. So, doing a "SetVersion;Build" doesn't work because
"Build" does a "Clean" first.
Expose a "BuildWithVersion" target instead.
--HG--
branch : dev
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
Added bits from SpecFlow 1.2 install
Added lib/specflow libraries and nearly empty Spec test project
Updating Orchard.proj to use NUnit task and locate test projects by pattern instead of fixed list
--HG--
branch : dev
Custom msbuild task performs heavy lifting over csproj xml
Project references are changed to file references, additional content files are added, and code files are copied over
--HG--
branch : dev
Failed test will stop the build. Results are in build\OrchardTests.xml.
Source zip should be able to open and run in visual studio.
--HG--
branch : dev
Initially contains Clean, Compile, Stage targets.
Default target, Build, calls each in order.
All outputs end in /build folder, which is ignored for source control purposes
--HG--
branch : dev
