TFS发布构建Powershell脚本看不到导入模块的命令

Question

We have a TFS build process using a custom template. The build works fine with the crm solution files successfully being created. We are then attempting to run a powershell script on the post build. This script imports a module. But the commands in the module are not being exposed. Whenever we attempt to invoke a command, we get an error. Along the lines of

The term 'Get-XrmSolution' is not recognized as the name of a cmdlet, function, script file, or operable program.

It doesn't matter which command we use in that module, we get the same kind of error.

To troubleshoot, we have logged onto the build server under the identity of the build account and can successfully run the script we are attempting to run.

Putting some more output into the script to troubleshoot...

Get-Module lists Xrm.Framework.CI.PowerShell. - Good.

Get-Command -Module "Xrm.Framework.CI.PowerShell" returns nothing. From the console, a number of commands are listed.

Is there something we need to do with the running of powershell post build scripts to enable the contents of an imported module to be seen?

Answer 1

IIRC you have to explicitly import the module with no assumption of being loaded on user profile, nor on the script path. Suppose Module1.psm1 is in the same folder as your script, use something like

Import-Module (Join-Path (Split-Path -Parent $MyInvocation.MyCommand.Definition) 'Module1.psm1')

Answer 2

Watch out for the bitness of PowerShell invoked by MSBuild and likewise, the bitness of MSBuild launched by Visual Studio. Certain modules only run in either 32-bit or 64-bit PowerShell and not both. You want to make sure the correct version of PowerShell is getting launched.

Answer 3

I had the same problem.

The module was loaded in the 'C:\\Program Files\\WindowsPowerShell\\Modules' folder (64 bits).

It all seemed fine when I logged on as the user, but it failed during TFS build.

Solution: I had to uninstall the module in PowerShell 64 bit and re-install in PowerShell 32 bit.

The module was then installed in 'C:\\Program Files (x86)\\WindowsPowerShell\\Modules' folder.