New features

[stej]

Hey guys,

I'm just curious if you have any idea for new features waiting just
for implementation.
Or if you consider psake as finished module that should be possibly
extended by users itself (custom modules,).

Thanks, stej

(I'm asking because I started with support for nunit and VS csprojs,
but I'm not sure if it should be distributed with psake or ot its own.)

--
You received this message because you are subscribed to the Google Groups "psake-dev" group.
To post to this group, send email to psak...@googlegroups.com.
To unsubscribe from this group, send email to psake-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/psake-dev?hl=en.

[Eric Hexter]

Can you describe what you have done with some more detail?

sent from my mobile phone

[stej]

I added working with csprojs like this:

PS>> $csp = Get-Csprojs c:\temp\UdpLogViewer\
PS>> $csp | Get-CsprojInfo | ft OutputType,AssemblyName, Signed,
SignKey, RootNamespace, Framework, Path, Directory

OutputType AssemblyName Signed SignKey
RootNamespace Framework Path Directory
---------- ------------ ------ -------
------------- --------- ---- ---------
Library CommonRules False
stej.Tools.U... v4.0 C:\temp\UdpL... C:\temp\UdpL...
Exe ConsoleViewer False
stej.Tools.U... v4.0 C:\temp\UdpL... C:\temp\UdpL...
WinExe FormsViewer False
stej.Tools.U... v4.0 C:\temp\UdpL... C:\temp\UdpL...
Library FormsViewer.Test False
FormsViewer.... v4.0 C:\temp\UdpL... C:\temp\UdpL...
Exe IpyHostingBen... False
IpyHostingBe... v4.0 C:\temp\UdpL... C:\temp\UdpL...
Exe TestUdpEmitor False
TestUdpEmitor v4.0 C:\temp\UdpL... C:\temp\UdpL...
Library UdpLogViewerCore False
stej.Tools.U... v4.0 C:\temp\UdpL... C:\temp\UdpL...


PS>> $csp | Get-CsprojDependencies | fl AssemblyName,@{N='References';
E={$_.References -join "`n" } }

AssemblyName : CommonRules
References : C:\temp\UdpLogViewer\UdpLogViewerCore
\UdpLogViewerCore.csproj

AssemblyName : ConsoleViewer
References : C:\temp\UdpLogViewer\UdpLogViewerCore
\UdpLogViewerCore.csproj

AssemblyName : FormsViewer
References : C:\temp\UdpLogViewer\CommonRules\CommonRules.csproj
C:\temp\UdpLogViewer\UdpLogViewerCore
\UdpLogViewerCore.csproj

AssemblyName : FormsViewer.Test
References : C:\temp\UdpLogViewer\CommonRules\CommonRules.csproj
C:\temp\UdpLogViewer\UdpLogViewerCore
\UdpLogViewerCore.csproj
C:\temp\UdpLogViewer\FormsViewer\FormsViewer.csproj

AssemblyName : IpyHostingBenchmark
References : C:\temp\UdpLogViewer\UdpLogViewerCore
\UdpLogViewerCore.csproj

AssemblyName : TestUdpEmitor
References :

AssemblyName : UdpLogViewerCore
References :

Why I added the dependency checking is described here:
http://www.leporelo.eu/blog.aspx?id=resolve-csproj-dependencies-when-projects-are-dependent-on-assemblies-from-bin
(the real reason is that I needed to handle dependencies on
assemblies, not only on projects)

------

Considering nunit, I simplified it like this:
nunit -assembly $dllPath -Exclude Slow -silent
(but I'm not sure if this is the right way)

On May 5, 2:31 am, Eric Hexter <eric.hex...@gmail.com> wrote:
> Can you describe what you have done with some more detail?
>
> sent from my mobile phone
>

> On May 4, 2010 5:07 PM, "stej" <cerna.ze...@seznam.cz> wrote:
>
> Hey guys,
>
> I'm just curious if you have any idea for new features waiting just
> for implementation.
> Or if you consider psake as finished module that should be possibly
> extended by users itself (custom modules,).
>
> Thanks, stej
>
> (I'm asking because I started with support for nunit and VS csprojs,
> but I'm not sure if it should be distributed with psake or ot its own.)
>
> --
> You received this message because you are subscribed to the Google Groups
> "psake-dev" group.
> To post to this group, send email to psak...@googlegroups.com.
> To unsubscribe from this group, send email to

> psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>
> .
> For more options, visit this group athttp://groups.google.com/group/psake-dev?hl=en.

>
> --
> You received this message because you are subscribed to the Google Groups "psake-dev" group.
> To post to this group, send email to psak...@googlegroups.com.
> To unsubscribe from this group, send email to psake-dev+...@googlegroups.com.

> For more options, visit this group athttp://groups.google.com/group/psake-dev?hl=en.

[Eric Hexter]

Those both sound interesting.  I personally would probably not use the functionality you described. I wonder if a psake-contrib or psake-extentions home would make sense..  they could be created as a number of modules and psake could look for an extensions folder and load each of the modules it finds...  just a though on a way that could the project could host all sorts of goodness without cluttering up the main module for those who do not want the core to grow.

Eric Hexter

Director of OSS | Headspring | www.Headspring.com
email | ehe...@Headspring.com
blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

[Jorge Matos]

I think that's a great idea !  Whoever wants to implement - go for it - I will try it out too - I would like to see what other folks might come up with.

--
Jorge Matos
Senior .NET Architect, MCSD.NET, MCSD Visual Studio 6.0
(440) 666-3107
matos...@hotmail.com      
Blog: http://jorgelmatos.blogspot.com
--------------------------------------------------------------------------------
"Any intelligent fool can make things bigger and more complex...
It takes a touch of genius - and a lot of courage to
move in the opposite direction."... - Albert Einstein

[stej]

Basically I created 2 modules - visualstudio.psm1 (only stuff with
csprojs currently) and nunit (simple wrapper for nunit-console
execution). I'm still looking for best way how to integrate it to
psake. Currently I added function Add-Module that should be used from
psake script. But this is certainly not final solution.

The changes are here: http://github.com/stej/psake/commit/c4e5f7ecdcd5497b00499831083c32c7cce1564e

On May 5, 6:59 pm, Eric Hexter <eric.hex...@gmail.com> wrote:
> Those both sound interesting.  I personally would probably not use the
> functionality you described. I wonder if a psake-contrib or psake-extentions
> home would make sense..  they could be created as a number of modules
> and psake could look for an extensions folder and load each of the modules
> it finds...  just a though on a way that could the project could host all
> sorts of goodness without cluttering up the main module for those who do not
> want the core to grow.
>
> Eric Hexter
>
> Director of OSS | Headspring |www.Headspring.com

> email | ehex...@Headspring.com

> >http://www.leporelo.eu/blog.aspx?id=resolve-csproj-dependencies-when-...

> > (the real reason is that I needed to handle dependencies on
> > assemblies, not only on projects)
>
> > ------
>
> > Considering nunit, I simplified it like this:
> > nunit -assembly $dllPath -Exclude Slow -silent
> > (but I'm not sure if this is the right way)
>
> > On May 5, 2:31 am, Eric Hexter <eric.hex...@gmail.com> wrote:
> > > Can you describe what you have done with some more detail?
>
> > > sent from my mobile phone
>
> > > On May 4, 2010 5:07 PM, "stej" <cerna.ze...@seznam.cz> wrote:
>
> > > Hey guys,
>
> > > I'm just curious if you have any idea for new features waiting just
> > > for implementation.
> > > Or if you consider psake as finished module that should be possibly
> > > extended by users itself (custom modules,).
>
> > > Thanks, stej
>
> > > (I'm asking because I started with support for nunit and VS csprojs,
> > > but I'm not sure if it should be distributed with psake or ot its own.)
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "psake-dev" group.
> > > To post to this group, send email to psak...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>

> > <psake-dev%2Bunsu...@googlegroups.com<psake-dev%252Buns...@googlegroups.com>

>
> > > .
> > > For more options, visit this group athttp://
> > groups.google.com/group/psake-dev?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "psake-dev" group.
> > > To post to this group, send email to psak...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>
> > .
> > > For more options, visit this group athttp://
> > groups.google.com/group/psake-dev?hl=en.
>
> > --
> >  You received this message because you are subscribed to the Google Groups
> > "psake-dev" group.
> > To post to this group, send email to psak...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>
> > .

[Dustin Venegas]

I am all for a psake-contrib. I think ayende's powershell extensions might be good in there as well.

http://github.com/ayende/Texo/blob/master/psake_ext.ps1

--
Dustin Eric Venegas
Dustin....@gmail.com

[stej]

I agree. But I think at the same time that there has to be a support
from psake. Consider this script:

build.ps1>>>>>>
properties {
$nunit = 'c:\temp\nunit-console.exe'
}
Import-Module nunit -argument $nunit
task default -depens tests
task tests {
Run-Nunit....
}
<<<<

Line "Import-Module nunit -argument $nunit" is called during
processing of the script, even before parameters and properties are
set. That's too early and that's why $nunit is $null at this time.

Instead I would call something like this:
Modules {
Import-Module nunit -argument $nunit
}
where Modules is function just like Properties but is called from
Invoke-Psake after all the parameters and properties are set.

On May 6, 5:55 pm, Dustin Venegas <dustin.vene...@gmail.com> wrote:
> I am all for a psake-contrib. I think ayende's powershell extensions might
> be good in there as well.
>
> http://github.com/ayende/Texo/blob/master/psake_ext.ps1
>
>
>
> On Wed, May 5, 2010 at 3:55 PM, stej <cerna.ze...@seznam.cz> wrote:
> > Basically I created 2 modules - visualstudio.psm1 (only stuff with
> > csprojs currently) and nunit (simple wrapper for nunit-console
> > execution). I'm still looking for best way how to integrate it to
> > psake. Currently I added function Add-Module that should be used from
> > psake script. But this is certainly not final solution.
>
> > The changes are here:

> >http://github.com/stej/psake/commit/c4e5f7ecdcd5497b00499831083c32c7c...

> > > > <psake-dev%2Bunsu...@googlegroups.com<psake-dev%252Buns...@googlegroups.com>
> > <psake-dev%252Buns...@googlegroups.com<psake-dev%25252Bun...@googlegroups.com>

>
> > > > > .
> > > > > For more options, visit this group athttp://
> > > > groups.google.com/group/psake-dev?hl=en.
>
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "psake-dev" group.
> > > > > To post to this group, send email to psak...@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>
> > <psake-dev%2Bunsu...@googlegroups.com<psake-dev%252Buns...@googlegroups.com>
>
> > > > .
> > > > > For more options, visit this group athttp://
> > > > groups.google.com/group/psake-dev?hl=en.
>
> > > > --
> > > >  You received this message because you are subscribed to the Google
> > Groups
> > > > "psake-dev" group.
> > > > To post to this group, send email to psak...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>
> > <psake-dev%2Bunsu...@googlegroups.com<psake-dev%252Buns...@googlegroups.com>
>
> > > > .

> > > > For more options, visit this group at
> > > >http://groups.google.com/group/psake-dev?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "psake-dev" group.
> > > To post to this group, send email to psak...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>
> > .
> > > For more options, visit this group athttp://
> > groups.google.com/group/psake-dev?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "psake-dev" group.
> > To post to this group, send email to psak...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > psake-dev+...@googlegroups.com<psake-dev%2Bunsu...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/psake-dev?hl=en.
>
> --

> Dustin Eric Venegas
> Dustin.Vene...@gmail.com

[stej]

It would be also great if anybody had some open source graph
visualization tool. Why? To display tasks dependencies.
I somewhat hacked yuml, so one gets nice picture, but it is limited by
max. url length. Have a look at http://github.com/stej/psake/commit/fdae80c51dc13b9a460ac92a2dd2d93217ae3da3

function Show-TasksGraph
and its usage in if ($docs) block

[stej]

Example:
http://yuml.me/diagram/scruffy/class/[full]->[Rebuild],[full]->[RunTests],[full]->[CleanBin],[full]->[CopyToBin],[rebuild]->[Clean],[rebuild]->[Build],[rebuildonly]->[Rebuild],[default]->[Full],[publish]->[CleanBin],[publish]->[CopyToBin]

On May 6, 11:13 pm, stej <cerna.ze...@seznam.cz> wrote:
> It would be also great if anybody had some open source graph
> visualization tool. Why? To display tasks dependencies.
> I somewhat hacked yuml, so one gets nice picture, but it is limited by

> max. url length. Have a look athttp://github.com/stej/psake/commit/fdae80c51dc13b9a460ac92a2dd2d9321...

> ...
>
> read more »

[Eric Hexter]

That is cool

[Steve Wagner]

I would really like to have an PSakeContrib project (which should be
also hosted by James because is easier to find) where we can find
modules for the most common psake operations.

>>>>>>> Director of OSS | Headspring |www.Headspring.com<http://www.headspring.com/>
>>>>>>> email | ehex...@Headspring.com
>>>>>>> blog |http://Hex.LosTechies.com<http://hex.lostechies.com/>

>>>>>>>> <psake-dev%2Bunsu...@googlegroups.com<psake-dev%252Buns...@googlegroups.com>
>> <psake-dev%252Buns...@googlegroups.com<psake-dev%25252Bun...@googlegroups.com>
>>>
>>>>>> <psake-dev%252Buns...@googlegroups.com<psake-dev%25252Bun...@googlegroups.com>
>> <psake-dev%25252Bun...@googlegroups.com<psake-dev%2525252Bu...@googlegroups.com>

[Jorge Matos]

It seems that support for a psakecontrib project would be a welcome addition.    

 

by the way stej,

 

if you changed your code from:

 

properties {
 $nunit = 'c:\temp\nunit-console.exe'
}
Import-Module nunit -argument $nunit
task default -depens tests
task tests {
 Run-Nunit....
}

to:

 

build.ps1>>>>>>
properties {
 $nunit = 'c:\temp\nunit-console.exe'
}

task default -depens tests
task tests {

 Import-Module nunit -argument $nunit 
 Run-Nunit....
}

 

it should work.

--
Jorge Matos
Senior .NET Architect, MCSD.NET, MCSD Visual Studio 6.0
(440) 666-3107
matos...@hotmail.com      
Blog: http://jorgelmatos.blogspot.com
--------------------------------------------------------------------------------
"Any intelligent fool can make things bigger and more complex...
It takes a touch of genius - and a lot of courage to
move in the opposite direction."... - Albert Einstein

[Eric Hexter]

How do you feel about auto importing all the modules in the current directory or some well known subfolder?

sent from my mobile phone

On May 7, 2010 3:47 PM, "Jorge Matos" <matos...@gmail.com> wrote:

It seems that support for a psakecontrib project would be a welcome addition.    

 

by the way stej,

 

if you changed your code from:

 
properties {
 $nunit = 'c:\temp\nunit-console.exe'
}
Import-Module nunit -argument $nunit

task de...

to:

 

build.ps1>>>>>>
properties {
 $nunit = 'c:\temp\nunit-console.exe'
}

task default -depens tests
task tests {

 Import-Module nunit -argument $nunit 

 Run-Nunit....
}

 

it should work.

On Fri, May 7, 2010 at 2:18 AM, Steve Wagner <li...@lanwin.de> wrote:
>

> I would really like to hav...

--
Jorge Matos
Senior .NET Architect, MCSD.NET, MCSD Visual Studio 6.0
(440) 666-3107

matos_jorge...

You received this message because you are subscribed to the Google Groups "psake-dev" group.

To post...

[Jorge Matos]

I like that idea - that should be easy to implement too.

 

something like:

 

function LoadModules()

{

    dir .\psake-contrib\*.psm1 | import-module

}

it could be called from within psake before any of the tasks are executed. 

[Eric Hexter]

Yea so then you just decide what modules you want by controlling what you keep in your build project.  I can see a module that knows how to enumerate the latest contrib modules from github and downloads them..

sent from my mobile phone

On May 7, 2010 4:20 PM, "Jorge Matos" <matos...@gmail.com> wrote:

I like that idea - that should be easy to implement too.

 

something like:

 

function LoadModules()

{

    dir .\psake-contrib\*.psm1 | import-module

}

it could be called from within psake before any of the tasks are executed. 

On Fri, May 7, 2010 at 4:04 PM, Eric Hexter <eric....@gmail.com> wrote:

>
> How do you feel about auto importing all the modules in the current directory or some well known...

>>
>> On May 7, 2010 3:47 PM, "Jorge Matos" <matos...@gmail.com> wrote:
>>

>> It seems that supp...

--

> You received this message because you are subscribed to the Google Groups "psake-dev" group.

> To post to this group, send email to psak...@googlegroups.com.

> To unsubscribe from this group,...

--

You received this message because you are subscribed to the Google Groups "psake-dev" group.

To post to this group, send email to psak...@googlegroups.com.

To unsubscribe from this group, sen...

[stej]

Sorry for previous (empty) answer :)

properties {
$nunit = 'c:\temp\nunit-console.exe'
}
task default -depens tests
task tests {
Import-Module nunit -argument $nunit
Run-Nunit....
}

will definitelly work. I used it for some time like this, but then
reconsidered.
The reason why I added special function for importing modules is
efficiency: If I have more tasks that use nunit, I would need to
import the module in each of them. If the module initialization would
be costly (not the case of nunit module now).
I could also use " if (!(get-module nunit)) { import-module
nunit... }", that is also possible, but ugly...

That's why I think special function should be introduced. It's
basically the same case as with Includes function.

> >> On Thu, May 6, 2010 at 4:16 PM, stej<cerna.ze...@seznam.cz>  wrote:
>
> >>   Example:

> >>>http://yuml.me/diagram/scruffy/class/[full]-<http://yuml.me/diagram/scruffy/class/%5Bfull%5D->

> ...
>
> číst dál »

[stej]

In case the module needs some arguments, it won't be possible.
(it is called like this: Import-Module nunit.psm1 -arguments c:\...
\nunit-console.exe
For example you need to setup path to some executables that are used
in the modules (nunit is one example).

On 7 kvě, 23:04, Eric Hexter <eric.hex...@gmail.com> wrote:
> How do you feel about auto importing all the modules in the current
> directory or some well known subfolder?
>
> sent from my mobile phone
>

[stej]

Do you have any code that would demonstrate it?

I really think autoloading modules is a bad way. Why?
- Efficiency. What if the module during initialization needs to check
something on network? Could be very slow. And even I need only one
specific module from modules directory, all others will be imported as
well because of automatic import?
- Initialization. Some modules will need some information about e.g.
executables they use (I already mentioned it in other answer)

On 7 kvě, 23:35, Eric Hexter <eric.hex...@gmail.com> wrote:
> Yea so then you just decide what modules you want by controlling what you
> keep in your build project.  I can see a module that knows how to enumerate
> the latest contrib modules from github and downloads them..
>
> sent from my mobile phone
>

> On May 7, 2010 4:20 PM, "Jorge Matos" <matos.jo...@gmail.com> wrote:
>
> I like that idea - that should be easy to implement too.
>
> something like:
>
> function LoadModules()
> {
>     dir .\psake-contrib\*.psm1 | import-module}
>
> it could be called from within psake before any of the tasks are executed.
>
>
>
> On Fri, May 7, 2010 at 4:04 PM, Eric Hexter <eric.hex...@gmail.com> wrote:
>
> > > How do you feel about auto importing all the modules in the current
> > directory or some well known...
>

[stej]

My mistake - if module is loaded, it is not reloaded by default. So
it's safe to use just "import-module nunit... " without the "if
condition".

[stej]

There is also one more possiblity that doesn't require any other
changes:

build.ps1>>>>>>
properties {
$nunit = 'c:\temp\nunit-console.exe'}

task default -depens testsAssembly1, testsAssembly2
task testsAssembly1 -depends initNunit {
Run-Nunit....}
task testsAssembly2 -depends initNunit {
Run-Nunit....}
task initNunit {
Import-Module nunit -argument $nunit
}
<<<<<
So all the import can be done in separate task. Not beautill, not
obvious, but easy and working.
If modules would be loaded like this, imported functions could be
imported via custom task as well. and Imports function won't be
needed, right?

[James Kovacs]

Sounds like there is a lot of support for a psake-contrib project. I've created one.

http://github.com/JamesKovacs/psake-contrib

Feel free to fork and send me pull requests...

James
--
James Kovacs, B.Sc., M.Sc., MCSD, MCT
Microsoft MVP, ASP/ASP.NET
http://www.jameskovacs.com
jko...@post.harvard.edu | @jameskovacs
403-397-3177 (mobile)

[Jorge Matos]

Wonderful!

Thank you James!

stej - your latest code sample makes sense but I agree there should be a better way to do that.

So far we have the following ideas:

1) psake can auto-load modules from a well-known local folder (".\psake-contrib") -  There would not be a way to pass parameters to your module during the import.

2) psake can auto-download modules from the git-hub psake-contrib repository 

3) Create a new psake function for loading modules explicitly - "Load-Module"
  i.e.

      properties {
           $module1path = ".\module1.psm1";
           $module2path = ".\module2.psm1";
      }

     load-module $module1path
     load-module $module2path
     ...

    or
    "Load-Modules"
 
     properties {
           $module_dir = ".\my_modules";
      }

     load-modules $module_dir

---------------------------------------------------------------------------------------------------

hmmm - I kind of like all these ideas.

Maybe we implement all of the ideas above and #1 and #2 are only enabled if you turn on the right configuration option in the $psake variable.

i.e.
$psake.auto_import_local_modules
$psake.auto_download_modules

Thoughts?