Skip to main content

Office 365 PnP-PowerShell 2013: Setup your machine part

Image
By
To run the PowerShell on your client machine you need to first step your client machine.
Here are the some of the tools, I would recommend you to install on your machine before going ahead any other development.




Install PNP Framwork on your client machine.

Free DLL(s) built and developed by Microsoft. Join this community and be the part to get the latest updates, here is the link.

 You can download the 2016 version, if you working on latest version. As of now I have installed 2013 version.
  • Download the binaries from following URL. You can use the most of the functionality/functions but not all. Because this client model mainly target to the office 365.
  • Once the files are installed you can go to its location and check the files.
  • You can copy this binaries and paste inside your build folder, because these are the dependencies that required for run the script. You can copy the SharePointPNPPowerShell2013 Folder and put into your final release file to give it your client. 
  • Download the files and include the module in your PS files.

Install Editor

I recommend you to install the visual studio code, it is very Powerful and support many languages one editor do multiple things as it is open source and you can use it on any platform like windows, mac etc. 
Configure the editor to run the PowerShell. 
  • You can download from this URL Install Visual Studio Code free editor.  
  • Install PowerShell extension.  
  • Check PowerShell console to run your script. Also debug your script.

Install Cmder to run your command

  • It is free tool very handy as compare with OOB command prompt. You can download this from this URL Good User Interface, nice shortcuts colorful view. Great feeling when you working on it.  
  • Support various tabs.  
  • Various settings.  
  • Support various scripting models like bash, Powershell and CMD.
Now your machine ready and start using PNP development.
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more