Adds support to defining an alias to a task.
Example:
  task Task_With_Descriptive_Name -alias twdn {}

By doing that I can now call .\psake.ps1 twdn and have the
Task_With_Descriptive_Name executed
fixes the task name when using aliases so that the casing is correct
fixing case where framework is set using 3 digits (3.0/4.0). The bit substring is empty, not null. This will fix all specs.
Merge pull request #26 from pedroreys/alias

Adds support to defining an alias to a task.
Defaulted psake to .NET 4.0
Switched to semantic versioning
Fixed formatting in .nuspec
Added test for issue with running a module function that depends on a function from another module
Adding ability to use a scriptblock when initializing an invoke-psake call in builds.
Merge pull request #30 from kblooie/DependantModuleIssue

Sample of the module dependency issue
Merge pull request #31 from idavis/master

Allow scriptblock execution for initialization step
Internal function names have been changed from Verb-Noun to VerbNoun (without dash) in an effort to reduce potential for external collisions.  Since external modules may be loaded with Verb-Noun naming after these internal functions are brought into scope, common functions like Resolve-Error are prone to get wiped out.. and to further lead to difficult to diagnose build problems.

See discussion https://github.com/psake/psake/issues/33
Minor tweaks to error output to make it consistent with what a build server like Jenkins might expect based on similarity to MSBuild output -- this is part one of the modification

Part two will involve incorporating a friendlier single line error message

https://github.com/psake/psake/issues/32
Replaced existing ResolveError with a modified variant that includes a short view, so that exceptions can be represented as one-liners for build output parsing purposes (it special cases Sql Exceptions as well to dig into the real errors)

Relies on new SelectObjectWithDefault function that can safely read properties off of objects w/out adding to the $Error collection (oddly, I've found this necessary when using WinRM, so I left that code in)

For instance, a short representation of an Error looks like this:
Error:  At C:\source\project\build\modules\Sql.psm1:175 char:36 +   [Void]$database.ExecuteNonQuery <<<< ($commands) [<<==>>] Exception: Exception calling "ExecuteNonQuery" with "1" argument(s): "ExecuteNonQuery failed for Database 'a73fa37f891e46bbab9e2b23b8f87c56'. " --> ExecuteNonQuery failed for Database 'a73fa37f891e46bbab9e2b23b8f87c56'.  --> An exception occurred while executing a Transact-SQL statement or batch. --> Foreign key 'fk_file_cabinet_num' references invalid column 'file_cabinet_num' in referencing table 'file_cabinet_files'.Could not create constraint. See previous errors. --> (Line [4] Proc
edure [] Class [16]  Number [1769] State [1] )

This is much more actionable / easier to read than 50 lines of output from an Exception with 4 InnerExceptions
The exit code from PowerShell was not being used as the exit code from the CMD script. This update fixes that so that the CMD script will exit with the same code that the PowerShell script exited with.
wrapping the chocolateyInstall in a try catch and changing the path to chocolatey install to use the environment variable ($env:ChocolateyInstall)
Added NuGet.exe so NuGetPackageBuilder.cmd will run without nuget having to be on the path.
Replaced NuGetPackageBuilder.cmd with a powershell equivalent (it's a powershell lib after all)
Bumped version to 4.2
Fixed package script to exclude nuget directory and nuget.ext. Bumped package version to 4.2.0.1