Description

Current implementation required VSSetup module to be installed in location where PowerShell can find it automatically. Now, before trying to import VSSetup, psake will check if it's not already loaded. This allows to work with VSSetup committed to repository, loading it either by psake-config.ps1 or manually in helper script.

Related Issue

Somewhat fixes #241, because now you don't have to install and maintain additional modules on build servers.

Motivation and Context

It's not always feasible to install additional modules on build server.

How Has This Been Tested?

I did not have VSSetup module installed. I have copied VSSetup module to a folder in repository. Then I modified psake-config.ps1 to include VSSetup.psd1 in $config.modules. After this psake used MSBuild 15 and build succeeded, whereas before the change it used version 14.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.