Existing file destroyed for lightweight databases
Tables dropped and recreated for client/server databases
This is "setup" only scenario. Recreating an orchard site on a new database will need some alternate "attach" mechanism - orthogonal to "setup" mechanism
--HG--
branch : dev
Sequence of events during setup functions at this point
Committing this point prior to cleaning up changes to ensure a working arrangement isn't lost
--HG--
branch : dev
Factoring references to Server.MapPath and HostingEnvironment.MapPath out of components
Building testing around setup package to isolate database deadlock
--HG--
branch : dev
Sites subdirectory may need to be created
Shouldn't write out the site-exists file until the setup transaction has committed
Host reinitialize should be called outside of the lifetime of the temporary shell to avoid a xact deadlock
--HG--
branch : dev
Needed for the setup scenario to be able to reload and apply new shell topology
Eventyally needed when module configuration requires the same effect
--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
build.cmd can take an optional target name like Compile or several targets in order with quotes like "Compile,Package"
clicktobuild.cmd will detect when the sdk env variable is not present, and vs2k8 is, and it will run the vs batch to initialize environment for calling msbuild
--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