| psdsctest | Psake | |
|---|---|---|
| 1 | 5 | |
| 1 | 1,536 | |
| - | 0.0% | |
| 0.0 | 0.0 | |
| about 2 years ago | over 1 year ago | |
| PowerShell | PowerShell | |
| - | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
psdsctest
Posts with mentions or reviews of psdsctest.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-08.
Psake
Posts with mentions or reviews of Psake.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-08.
-
Achieving single command Infrastructure deployment using PowerShell DSC.
You may use other tools too: psake, make, cake, fake or any other *ake you are familiar with. I look at them as a tools that make build tasks behind simple commands and help me answer: How did I run that code again?
- How do you guys make sense of a complex project on GitHub?
-
How do you specify Debug or Release when calling Invoke-psake?
I use the psake PowerShell module to "build" my PowerShell modules. My psakefile.ps1 contains the logic needed to update the manifest with an incremented version, any new function/cmdlet names, and so on. Then it copies everything from .\src\ to .\output\modulename\version. All I do is call Invoke-psake build or Invoke-psake test, and this works great as-is for "pure powershell modules".
-
What build tool(s) do people use for their applications?
I've used psake (powershell+make) https://github.com/psake/psake - the main thing that attracted me to this was that it wasn't an XML based system (Nant/MSbuild), and it handled task prerequisites very nicely. While some devs find powershell a bit of a pain to learn, they generally become useful very quickly, and I think it's useful to be able to do some level of powershelling anyway.
-
pake: Just another Make but with Powershell
GitHub - psake/psake: A build automation tool written in PowerShell
What are some alternatives?
When comparing psdsctest and Psake you can also consider the following projects:
Invoke-BuildResolve-MSBuild.ps1
Cake - :cake: Cake (C# Make) is a cross platform build automation system.
Invoke-BuildInvoke-Build.ps1
Invoke-Build - Build Automation in PowerShell
Invoke-BuildBuild-Parallel.ps1
MSBuild - The Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio.
NUKE - 🏗 The AKEless Build System for C#/.NET
Invoke-BuildBuild-Checkpoint.ps1
FAKE - FAKE - F# Make
CS Make - Sake Build
psdsctest vs Invoke-BuildResolve-MSBuild.ps1
Psake vs Cake
psdsctest vs Invoke-BuildInvoke-Build.ps1
Psake vs Invoke-Build
psdsctest vs Invoke-BuildBuild-Parallel.ps1
Psake vs MSBuild
psdsctest vs Invoke-Build
Psake vs NUKE
psdsctest vs Invoke-BuildBuild-Checkpoint.ps1
Psake vs FAKE
psdsctest vs Cake
Psake vs CS Make