Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

developer:zoowhat [2015/09/14]
127.0.0.1 external edit
developer:zoowhat [2016/02/12] (current)
sandy
Line 1: Line 1:
 ====== What is a Zoo Plug-in? ====== ====== What is a Zoo Plug-in? ======
 > **Developer:​** //​[[developer:​zoo|Zoo 5.0]]// > **Developer:​** //​[[developer:​zoo|Zoo 5.0]]//
-> **Summary:​** //Overview of plug-ins for Zoo 5.0.//+> **Summary:​** //Overview of plug-ins for Zoo 5.0//
  
-===== Overview ===== +A Zoo plug-in is a software module, developed by a third party, that extends the functionality of Zoo 5.0 by letting ​it validate product licenses.
-A Zoo plug-in is a software module, developed by a 3rd party, that extends the functionality of Zoo 5.0 by allowing ​it to validate product licenses.+
  
-===== More Information ​===== +===== More information ​===== 
-The Zoo lets you share licenses, or CD-Keys, among users. ​Prior to Zoo 5.0, the only licenses that could be shared by the Zoo were from McNeel-based products (i.e. Rhino, Flamingo, Penguin, Brazil, and Bongo). With Zoo 5.0, 3rd party Rhino plug-in developers can now add support for their products to the Zoo.+The Zoo lets you share licenses, or CD-Keys, among users. ​Before ​Zoo 5.0, the only licenses that could be shared by the Zoo were from McNeel-based products (i.e. Rhino, Flamingo, Penguin, Brazil, and Bongo). With Zoo 5.0, third party Rhino plug-in developers can now add support for their products to the Zoo.
  
 {{:​developer:​zoopluginaddlicense.png|}} {{:​developer:​zoopluginaddlicense.png|}}
  
-When Rhino and Rhino-baed products are installed as workgroup nodesinstead of standalone ​nodes, licensing works like this:+When Rhino and Rhino-based products are installed as workgroup nodes instead of stand-alone ​nodes, licensing works like this:
  
   * When a workgroup node starts, it requests a license from the Zoo.   * When a workgroup node starts, it requests a license from the Zoo.
Line 18: Line 17:
  
 =====What is required to build a plug-in?​===== =====What is required to build a plug-in?​=====
-Zoo plug-ins are .NET Framework 4.0 assemblies. ​Thus, to create a plug-in for Zoo 5.0, you will need one of the following development tools:+Zoo plug-ins are .NET Framework 4.0 assemblies. ​So, to create a plug-in for Zoo 5.0, you need one of the following development tools:
  
   - Microsoft Visual C# 2010   - Microsoft Visual C# 2010
   - Microsoft Visual Basic .NET 2010   - Microsoft Visual Basic .NET 2010
  
-Also, all plug-ins that use the Zoo license system must be signed with an Authenticode certificate issued by McNeel Plugin Security. These certificates are free, but must be requested by each developer. Developers must agree to the //Terms of Use// before a certificate is issued. For more information on plug-in signing, see the following +Also, all plug-ins that use the Zoo license system must be signed with an Authenticode certificate issued by McNeel Plugin Security. These certificates are free, but must be requested by each developer. Developers must agree to the //Terms of Use// before a certificate is issued. For more information on plug-in signing, see [[developer:​digital-signatures/​create-request|Digitally Signing Plug-ins.]]
- +
-[[developer:​digital-signatures/​create-request|Digitally Signing Plug-ins]]+
  
 \\ \\
developer/zoowhat.txt · Last modified: 2016/02/12 by sandy