RE: QuickApps and PowerShell Commands

RE: QuickApps and PowerShell Commands

Home Forums QuickApps Forum QuickApps and PowerShell Commands RE: QuickApps and PowerShell Commands


Hi John,

To deploy QuickApps from the SharePoint Management Shell you would do the following:


1. Run Add-SPSolution to upload the .wsp package to the farm.


     e.g. Add-SPSolution "C:\Downloads\Quick.Apps.wsp"


2. Run Install-SPSolution to schedule deployment of the package to one or more Web Applications. Make sure that the SharePoint Administration service is running before executing this cmdlet.


     e.g. Install-SPSolution -Identity Quick.Apps.wsp -GACDeployment -AllWebApplications


   When this cmdlet finishes, it does not mean that the deployment has completed. You can use Get-SPSolution to check the status of the deployment job.


This next step is not absolutely necessary, but it is recommended. Each Web Application has a QuestConfiguration feature that will add the essential entries to the web.config file for the web application. You can do this manually with the Configuration Editor, but the QuestConfiguration feature automates this process (mostly). Run the following cmdlet to activate this feature:

     e.g. Enable-SPFeature -Identity QuestConfiguration -Url http://mywebapplication


Next you should activate the remaining features as required using the Enable-SPFeature cmdlet. The features to be activated are listed here:


          – QuestLists – Site Feature

          – QuestWebParts – Site Collection Feature

          – QuestMyFirstApp – Site Feature in version 6.0 (Moved to the Site Collection in version 6.1)

For example:

     Enable-SPFeature -Identity QuestWebParts -Url http://mywebapplication/mysitecollection

Version 6.0 of QuickApps had a dependency between QuestMyFirstApp and QuestWebParts. If you are going to activate QuestMyFirstApp, make sure you activate the QuestWebParts feature first.

If you are going to put it into a script, there are numerous enhancements that you can make. For example, you can use the following cmdlets to iterate through the WebApplications, Site Collections and SubSites to simplify the activation of features:





After running the PowerShell cmdlets, you should run the Configuration Editor to add any remaining settings to the web.config file. These remaining settings are not essential to the core functionality of the Web Parts, but they are necessary for the proper functioning of some advanced features.

Let me know if you have any questions.

Bill Armstrong