Powershell MSBuild Task

Source code checked in, #52406

_TFSSERVICE — Tue, 20 Jul 2010 20:45:25 GMT

Checked in by server upgrade

New Post: MSBuild Powershell Task Factory

ArildFines — Thu, 25 Feb 2010 21:00:52 GMT

Looks to me like the same general idea? I'm not overly familiar with the ITaskFactory stuff; I'm guessing this is new for MSBuild 4.0, but I can see where you're going with it.

I'd say the integration with Powershell goes a little deeper in my project, and I'm not overly fond of the amount of ceremony you have to go through with the ITaskFactory stuff (declaring parameters etc). I'd probably consider implementing this as well, but then as an optional approach to the one I'm already using.

New Post: MSBuild Powershell Task Factory

aarnott — Tue, 23 Feb 2010 22:28:55 GMT

How do you feel this project relates to the MSBuild Powershell Task Factory?

Commented Issue: License in Setup is different [4755]

ArildFines — Tue, 08 Dec 2009 20:14:26 GMT

The MSI requires to accept a XYZ license, while the CodePlex project states a "Microsoft Public License (Ms-PL)".
The reason may be caused by not having changed the WiX default. License may be easily customized in WiX throught
<WixVariable Id="WixUILicenseRtf" Value="myLicense.rtf" />
The content of myLicense.rtf should obviously be Ms-PL to be coherent.

Source code checked in, #36485

ArildFines — Tue, 08 Dec 2009 20:09:29 GMT

Use the correct license in the installer, MS-PL.

Created Issue: License in Setup is different [4755]

giuliov — Thu, 26 Nov 2009 21:43:57 GMT

Patch Applied: #4522

ArildFines — Wed, 25 Nov 2009 19:42:57 GMT

ArildFines has applied patch #4522.

Comment:
Thanks for the patch(es). I saw no reason not to apply them.

Source code checked in, #35625

ArildFines — Wed, 25 Nov 2009 19:40:33 GMT

Patch from 'Thijs': Added an extra exception handler to be able to see on which line the executed powershell script breaks.

Source code checked in, #35623

ArildFines — Wed, 25 Nov 2009 19:34:13 GMT

Patch from 'Thijs': Implemented the Get for the Buffersize property in PSHostRawUserInterface to be able to use the Out-String cmdlet in script

Patch Uploaded: #4522

thijs — Wed, 25 Nov 2009 17:03:55 GMT

thijs has uploaded a patch.

Description:
I added an extra exception handler to be able to see on which line the executed powershell script breaks. Helps a lot when a script doesn't run and you need to find out why :)
Also implemented the Get for the Buffersize property in PSHostRawUserInterface to be able to use the Out-String cmdlet in scripts. (Which lets you output entire objects when combined with Write-Host, also very handy when debugging your Powershell scripts).

The patch is made with the Codeplex "cpc" client, I hope you are willing to consider this.

Regards,
Thijs

New Post: Parameters don't seem to work for me

ArildFines — Fri, 06 Nov 2009 16:40:23 GMT

I've uploaded a new release that only contains the schema fix.

Updated Release: 0.6.0.1 (nov 06, 2009)

ArildFines — Fri, 06 Nov 2009 16:39:31 GMT

Added information about the ScriptFile attribute to the schema so that Intellisense is provided for this attribute.

Released: 0.6.0.1 (Nov 06, 2009)

Fri, 06 Nov 2009 16:39:31 GMT

Added information about the ScriptFile attribute to the schema so that Intellisense is provided for this attribute.

Source code checked in, #34472

ArildFines — Fri, 06 Nov 2009 16:35:00 GMT

Add information to the schema about the ScriptFile attribute for intellisense.

Source code checked in, #34469

ArildFines — Fri, 06 Nov 2009 16:25:37 GMT

Uh, no, this isn't about ASP.NET.

New Post: Parameters don't seem to work for me

ArildFines — Fri, 06 Nov 2009 16:20:56 GMT

Oops. I'll update the schema.

New Post: Parameters don't seem to work for me

eekstein — Fri, 06 Nov 2009 16:12:10 GMT

I figured out the problem. When running an external script you need to use the "ScriptFile" attribute. Although it briefly mentions this in the Usage link the schema that creates the intellisense is out-of-date so it does not show the ScriptFile attribute.

The correct form in my case is ...

New Post: Parameters don't seem to work for me

eekstein — Fri, 06 Nov 2009 02:48:59 GMT

I am sure I am doing something wrong but not sure what. I have tried to use your PowerShell task but it keeps telling me I am not passing in the parameters.

Here is the script I am trying to execute ...

F:\Builds\SSISDeployment\ssis-generate.ps1 -oldVersion 1.0.0.0 -src F:\Build\TestTask\Drop\SSIS\

The first line of the script looks like this...

Param([string]$oldVersion, [string]$src)

I have tried...

<PropertyGroup>
<oldVersion>1.0.0.0</oldVersion>
<src>$(SSISDropLocation)</src>
</PropertyGroup>
<Powershell Script="f:\Builds\SSISDeployment\ssis-generate.ps1" TaskItems="$(oldVersion);$(src)" />

...AND...

<PropertyGroup>
<Argument1>1.0.0.0</Argument1>
<Argument2>$(SSISDropLocation)</Argument2>
</PropertyGroup>
<Powershell Script="f:\Builds\SSISDeployment\ssis-generate.ps1" TaskItems="$(Argument1);$(Argument2)" />

All of these give the same result. The script returns telling me I need to pass in the parameters. What am I doing wrong?

New Post: Error executing script

jonesie — Tue, 18 Aug 2009 21:11:50 GMT

Next problem :) The HyperV stuff my script calls is in the profile for the TFSService which is running the build. The powershell task doesnt appear to be loading the profile. Aside frmo including the hyperv stuff in my script can you think of anyway this could work? It would also be cool if the task could runas a particular user. I think I will get the code at some point and have a hack.

Cheers

New Post: Error executing script

jonesie — Tue, 18 Aug 2009 20:30:00 GMT

THanks very much for that. It looks like there are only a couple of semi-colons in there - I normally dont bother with them so will try without. The scriptfile would be betterer though.

Cheers