This project is read-only.
Installing OrchardPs is quite simple, although it is more complicated than installing an Orchard module. This article assumes that you have downloaded a release package.

In order to use OrchardPs, you must set your PowerShell execution policy to at least 'Remote signed'. You can do this by running PowerShell as an administator and executing the following command:
Set-ExecutionPolicy RemoteSigned
OrchardPs consists of two parts - the OrchardPs console, which is a regular application, and the Proligence.PowerShell Orchard module which implements PowerShell support inside Orchard. To run OrchardPs you must install both of these components.

1. Unzip the package and copy the files to the root directory of your Orchard installation. If you won't be using Visual Studio, you can ignore the lib folder and copy only the src\Orchard.Web folder.

2. If you will be using Visual Studio then it's a good idea to add a reference to add the following references to the Orchard.Web project.
  • lib\orchardps\Orchard.Management.PsProvider.dll
  • lib\orchardps\OrchardPs.exe
  • lib\orchardps\Proligence.PowerShell.Vfs.dll
3. Start your Orchard application and enable the Proligence.PowerShell module in the admin.

4. Start OrchardPs by running the OrchardPs.exe console application from Orchard.Web\bin folder.

You may encounter errors due to invalid versions of libraries used by Orchard (such as Autofac). Different versions of Orchard use different libraries and OrchardPs tries to target the latest version of Orchard. If you need to use OrchardPs with an older or yet unreleased version of Orchard, you can easily change the version of the libraries used by OrchardPs using assembly binding redirect in the OrchardPs.exe.config file. You can find more info on this topic on MSDN (

Last edited Jun 18, 2013 at 12:56 PM by MpDzik, version 4


No comments yet.