369 packages tagged with “Powershell”
Runtime for hosting PowerShell
Native binaries for PowerShell Core
Runtime for Microsoft.Management.Infrastructure
MarkdownRenderer for PowerShell
PowerShell global tool
Command line tool for interactive programming with C#, F#, PowerShell, and more. Powers Polyglot Notebooks and provides .NET support for Jupyter.
psake is a build automation tool written in PowerShell. It avoids the angle-bracket tax associated with executable XML by leveraging the PowerShell syntax in your build scripts. psake has a syntax inspired by rake (aka make in Ruby) and bake (aka make in Boo), but is easier to script because it leverages your existent command-line knowledge. psake is pronounced sake - as in Japanese rice wine. It does NOT rhyme with make, bake, or rake. You can also install with chocolatey (http://nuget.org/List/Packages/chocolatey) and have global psake.
Contains the SDK reference assemblies for PowerShell version 5
Contains the reference assemblies for PowerShell Standard 5
Cake Build addon for Powershell.
A cross-platform pre-instrumenting code coverage tool set for .net/.net core and Mono
Invoke-Build is a build and test automation tool which invokes tasks defined in PowerShell v3.0+ scripts. It is similar to psake but arguably easier to use and more powerful. It is complete, bug free, well covered by tests.
Pester is testing framework for PowerShell, written in PowerShell.
Contains the SDK reference assemblies for PowerShell version 3
Contains the reference assemblies for PowerShell version 5.1
biz.dfch.PS.System.Logging ========================== Modules: biz.dfch.PS.System.Logging d-fens GmbH, General-Guisan-Strasse 6, CH-6300 Zug, Switzerland This PowerShell module contains Cmdlets that allow to perform logging from your PowerShell functions and code via the Apache Log4Net library. * You can also download this module via [NuGet](http://nuget.org) with [Install-Package biz.dfch.PS.System.Logging](https://www.nuget.org/packages/biz.dfch.PS.System.Logging/). * After downloading the package to a directory of your choice (_NOT_ the actual module directory) run the `install.ps1` script in the downloaded folder to copy the files to a directory inside `$ENV:PSModulePath`). * In case you already have a previous version of this module ( < 1.0.5) in a different module directory you have to remove that module manually. * In case you update the module in the same directory and the `log4net.dll` is still loaded you might have to restart all the PowerShell sessions to be able to overwrite the file. * In case you changed the log settings in `biz.dfch.PS.System.Logging.xml`, `Log4netConfiguration.xml` or `log4net.xml` you have to restore the changes as they will get overwritten. See http://d-fens.ch/2013/01/16/module-biz-dfch-ps-system-logging/ and the [Wiki](https://github.com/dfch/biz.dfch.PS.System.Logging/wiki) for more information.
Powershell scripts necessary for continuous integration.
Reporting interface for the firewall and the windows to support logging to disk as well as start Post-Reporting work-flows like PowerShel scripts or executables. The Package extends the reporting functionality to NuGet package Walter.Web.Firewall and is easily activated by dependency injection during service configuration services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute) , options => { //your options }).UseDiskLogging(opt=>{ opt.DataDirectory = @"D:\Web-FireWall\FireWall"; opt.PowerShellOption = PowerShellFilesOption.GenerateIfMissing; opt.Commandline = new System.Diagnostics.ProcessStartInfo(@"D:\jobs\FireWall.bat"){UseShellExecute = true}; }); More information on how to use this Add-On is available in this manual https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf