Comments on: Imtech Run PowerShell Script Deployment Step

By: Waldek Mastykarz

Waldek Mastykarz — Mon, 10 Oct 2011 03:07:22 +0000

@Nicole: I suggest you check out the code of CKS:DEV on CodePlex. We have built a custom extension that allows us to execute PowerShell scripts using the x64 PowerShell process.

By: Nicole

Nicole — Sat, 01 Oct 2011 09:55:31 +0000

Hi,

Great work! However, I have a question. I have a similar issue with Enric as I have read above. I want to execute Sharepoint powershell scripts such as creating new site, getting list of sites in a site collection, etc. from WCF in Visual Studio 2010. However, since VS is a 32 bit process it cannot execute 64bit powershell for Sharepoint cmdlets as you have said. Do you have any idea how to fix this?

Thank you very much!

By: Waldek Mastykarz

Waldek Mastykarz — Sun, 21 Aug 2011 08:34:37 +0000

@Galiya: This extension has been merged with CKS:DEV where it's being developed further, so if you are interested in the newest version you should install CKS:DEV. As for the functionality you mentioned, it has been reported to us before (http://cksdev.codeplex.com/workitem/6251). One thing you could do to have implemented faster is to vote on the issue.

Thank you for your feedback.

By: Galiya

Galiya — Fri, 19 Aug 2011 09:43:08 +0000

Hi Waldek,

When you add file to "powershell script #1", can you specify a relative path for the file? I have my ps1 file in the project folder itself, but on different dev machines it is located in the different location. At the moment, every developer has to change this property to deploy successfully. Do I miss something, or this is not yet available?

Thanks in advance,
Galiya

By: Kostadin Markov

Kostadin Markov — Fri, 03 Dec 2010 00:25:08 +0000

Ernic, I suggest setting $ErrorActionPreference = 'stop' within the script – may not help though!

By: Waldek Mastykarz

Waldek Mastykarz — Tue, 19 Oct 2010 04:04:56 +0000

@Michael: did you set the execution policy while running PowerShell as administrator or just like a plain user?

By: Michael Blumenthal

Michael Blumenthal — Mon, 18 Oct 2010 17:41:21 +0000

I just posted an issue at http://cksdev.codeplex.com/workitem/5732 – POSH refuses to run my script because it is unsigned and I don't seem to have any way to set the execution policy.

By: Enric

Enric — Tue, 20 Jul 2010 07:01:11 +0000

You've got it!

http://cksdev.codeplex.com/workitem/5214

By: Waldek Mastykarz

Waldek Mastykarz — Mon, 19 Jul 2010 17:12:10 +0000

@Enric: sure. I would appreciate it if you could add it to the Issue Tracker @ http://cksdev.codeplex.com so that we can note that, discuss with the team and if there is no blocks for it, include it in the next release.

Thanks again for your feedback,

Waldek

By: Enric

Enric — Mon, 19 Jul 2010 11:49:58 +0000

Just one thing, Waldek: after executing the PS1 script, the Process object returns ExitCode = 0 even if a command has failed, so the generated StandardError text is lost (in fact, I could only see it debugging the code).

if (cmd.ExitCode != 0)
{
logger.WriteLine(cmd.StandardError.ReadToEnd(), LogCategory.Error);
}

Do you think that the Standard Error could be always logged, regardless of the ExitCode?