Introducing the Data ONTAP PowerShell Toolkit Proxy

by Frequent Contributor on ‎2012-10-31 12:10 PM

Please note:  Use of the Data ONTAP PowerShell Toolkit Proxy is UNSUPPORTED.

Toolkit 2.1 included stable output types; Toolkit 2.2 expands upon this by introducing the Data ONTAP PowerShell Toolkit Proxy.  Attached to this post is everything you will need to get started developing .Net applications using the Data ONTAP PowerShell Toolkit.

There are 3 things included in the DataONTAP.Proxy archive attached to this post.

1) The DataONTAP.Proxy.dll.

2) "Getting Started with the Data ONTAP PowerShell Toolkit Proxy Library" document.

3) The "ProxySample" Visual Studio 2010 solution.

The Data ONTAP PowerShell Toolkit Proxy Library simplifies the development of applications built on the PowerShell Toolkit.  The Proxy handles the interaction with PowerShell, allowing the developer to focus more on the solution and less on PowerShell.

This is accomplished by transforming the Data ONTAP PowerShell module into a library. PowerShell cmdlet nouns turn into classes.  The verbs (and parameter set name) become methods inside of those classes.  For example, the cmdlet Get-NaVol is the Get() method in the NaVol class.  A Proxy class includes an instance of each of these PowerShell noun classes, making cmdlet invocations incredibly simple.  For example, if “ontapProxy” is an instance of the Proxy class, the line “ontapProxy.NaVol.Get()” would return all of the volumes on the current controller.

Please feel free to post feedback here!

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.