… default.

Also added columns order to format-table, to print them in nice order

…ild script dir wasn't respected

Now psake-config.ps1 from build script dir is loaded first, and then new psake context is created with newest $psake.config.taskNameFormat

…ck to includeFilename, because it's filename not block

Now it is possible to set some properties in psake-config.ps1 from psake.psm1 directory, but setting all is not required.
And it is possible to set another in psake.config.ps1 from build script directory.

… outputing colored messages

Updated change from 091cc67
Also changed colors used for task notification from darkgreen to blue
And all colors are in uppercase, this way call somwhere inside powershell.exe (exactly in System.Management.Automation.dll!System.Management.Automation.LanguagePrimitives.ConvertStringToEnum) will not throw exception (which is also handled there, so it's not an error)

…cations

Instead of single $psake.config (which could be changed in nested Invoke-Psake invocation, but wasn't cleaned afterwards) there is now $psake.context.Peek().config

Additional changes required to this to work:
 - task name format is only in psake config, not also in $psake.formatTaskName, same with $psake.framework_version
 - default config is now in separate property $psake.config_default
 - added Get-CurrentConfigurationOrDefault to get config from $psake.context.Peek().config if it exists or $psake.config_default otherwise
 - psake-config sets config into variable $config which is from Get-CurrentConfigOrDefault
 - updated spec/writing_psake_variables_should_pass
 - buildFile parameter to Invoke-Psake now doesn't have default value, if it's null build file from psake config is used

Conflicts:
	psake.psm1