Visual Studio Post Deployment Script - ALCM

Document created by Eric Harris Employee on May 20, 2016
Version 1Show Document
  • View in full screen mode

Automate the full process along with the way to apply the Continuous Integration & Continuous Deployment concepts.

 

AuthorAyman El-Hattab
Long DescriptionThis post is the first of a series and is going to deal with the first step towards Application Lifecycle Management for Nintex which is setting up your development environment. The goal of the post is to provide you with a way to manage your Nintex assets in Team Foundation Server so that any developer in the team can get the latest work from Team Foundation Server, click deploy and BOOOM, all the SharePoint & Nintex artifacts get deployed and published.
DependenciesVisual Studio
Support Info

Ayman El-Hattab - The Visual Studio Post Deployment Script For Nintex Workflows & Forms

Compatibility

Nintex Workflow 2013

Nintex Forms 2013

Platform

SharePoint Server 2013

Screenshots

Additional Information

Here are the steps:

1) Download the scripts from the post attachments. I've also added the SharePoint Project so you can quickly test the whole thing.

2) In the Visual Studio SharePoint Project, create a new folder and name it "NintexArtifacts".

3) Create a subfolder in the "Nintex Artifacts" folder for each list where you would like to publish the Workflows & Forms. Make sure to name the subfolders after the list instances.

4) In the Post-deployment Command Line, call the VisualStudioPostDeploymentScriptForNintex.ps1 . The script expects two parameters:

     - Project Folder Location (projectFolderLocation)

     - Site Collection URL (devSiteColUrl)

 

Here is what you should add in Visual Studio:

%windir%\sysnative\windowspowershell\v1.0\powershell -file "C:\DevScripts\Scripts\VisualStudioPostDeploymentScriptForNintex.ps1" -projectFolderLocation "$(ProjectDir)"" -devSiteColUrl "$(SharePointSiteUrl)"

 

If you're wondering why we are using "%windir%\sysnative\windowspowershell\v1.0\powershell" rather than directly calling the script, it's due to the fact that SharePoint is 64bit and Visual Studio is still 32bit. This means that Visual Studio will by default call the 32bit version of PowerShell resulting in errors. That's why we, instead, need to instruct Visual Studio to load the 64bit PowerShell by referencing "%windir%\sysnative\windowspowershell\v1.0\powershell".

 

5) Once you click "Deploy", here is what you should see in the Output Windows:

6) Once deployment is done, open your list and check whether the Workflows & Forms have been successfully published!!

Nintex Xchange Terms of Use Policy

Nintex makes no warranty or guarantee about the reliability, performance, quality, or functionality of any assets, and any assets you install are therefore provided as is. By downloading this asset, you agree to the terms of use.

1 person found this helpful

Outcomes