Running powershell in net4.0 mode?

[andreasohlund]

Are we 100% sure that we need to do this for nuget to work?

The reason I ask is that I have a hunch that it won't work on the buildservers since we can run as admin.

[Jpattom]

This is to identify the version from one of the dll
nuget can work without powershell

Currently the script for packing can have version in 3 diffrent ways

1. Pass as argument while creating the package
2. Set the global property of packit module before we start packing
3. It will be taken from the current build Assembly

only for the third we need powershell to use the .net4.0 (or latest installed considering the fact that build server has to have .net 4.0 installed if it has to build .net 4.0 Assemblies )

[andreasohlund]

only for the third we need powershell to use the .net4.0 (or latest installed considering the fact that build server has to have .net 4.0 installed if it has to build .net 4.0 Assemblies )It has 4.0 installed, I'm just worried that the runonce.bat thing will not be allowed to execute. We'll see I guess:)
/Andreas

http://andreasohlund.net

http://twitter.com/andreasohlund

Date: Tue, 14 Jun 2011 00:53:21 -0700
From: reply@reply.github.com
To: andreas_ohlund@hotmail.com
Subject: Re: [NServiceBus] Running powershell in net4.0 mode? (#68)

This is to identify the version from one of the dll
nuget can work without powershell

Currently the script for packing can have version in 3 diffrent ways

1. Pass as argument while creating the package
2. Set the global property of packit module before we start packing
3. It will be taken from the current build Assembly

only for the third we need powershell to use the .net4.0 (or latest installed considering the fact that build server has to have .net 4.0 installed if it has to build .net 4.0 Assemblies )

Reply to this email directly or view it on GitHub:
#68 (comment)

[Jpattom]

runonce and packit.ps1 would be temporary I would be moving runonce to
prepare.ps1 and the packit.ps1 to one of the task in default.ps1 with proper
checks and warnings

with packit.ps1 I was trying to modularise the packaging logic to
packit.psm1
once packi.psm1 and default.ps1 is ready we will be able retire packit.ps1

and hence we would be able to add task for packing each package from
default.ps1 with proper dependency

by the by

Am I doing little bit over engineering...........

On 14 June 2011 16:10, andreasohlund <
reply@reply.github.com>wrote:

only for the third we need powershell to use the .net4.0 (or latest
installed considering the fact that build server has to have .net 4.0
installed if it has to build .net 4.0 Assemblies )It has 4.0 installed, I'm
just worried that the runonce.bat thing will not be allowed to execute.
We'll see I guess:)
/Andreas

http://andreasohlund.net

http://twitter.com/andreasohlund

Date: Tue, 14 Jun 2011 00:53:21 -0700
From: reply@reply.github.com
To: andreas_ohlund@hotmail.com
Subject: Re: [NServiceBus] Running powershell in net4.0 mode? (#68)

This is to identify the version from one of the dll
nuget can work without powershell

Currently the script for packing can have version in 3 diffrent ways

1. Pass as argument while creating the package
2. Set the global property of packit module before we start packing
3. It will be taken from the current build Assembly

only for the third we need powershell to use the .net4.0 (or latest
installed considering the fact that build server has to have .net 4.0
installed if it has to build .net 4.0 Assemblies )

Reply to this email directly or view it on GitHub:

#68 (comment)

Reply to this email directly or view it on GitHub:
#68 (comment)

[andreasohlund]

That's fine, I think its good to break the build + packaging up into smaller pieces to make it easier to maintain