ignore the idiot who decided to enumerate a collection multiple times causing Bad Things
so i'm cool with us not throwing this exception right now
time to tone down some diagnostics
obsering when files are deleted so that we can ensure we end the complete the uninstall recursively
code tidy-up
added a test to recursively delete an arbitrary graph of files
Add -ReleasesDirectory to Create-Release and Create-ReleaseForProject
Nothing to see here.... move along.
Apply Powershell conventions with restraint.
move that IScheduler around
dropping the need to use AsyncSubject
Use NuGet helper methods
Directory.CreateDirectory does a recursive creation by default
Merge pull request #124 from github/use-helper-methods

Use helper methods
introduced scheduler parameter to DeleteDirectory
Merge pull request #126 from github/uninstall-should-be-amazing

Uninstall should be amazing
version bump to 0.6.23
corrected unit test refactoring
Merge branch 'pr/135'
version bump to 0.6.24