Site Tools


Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
developer:zoowhat [2020/11/24]
sandy [What is a Zoo Plug-in?]
developer:zoowhat [2020/11/24]
sandy [What is required to build a plugin?]
Line 6: Line 6:
  
 ===== More information ===== ===== More information =====
-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.+The Zoo lets you share licenses, or CD-Keys, among users. Before Zoo 5.0, the only licenses shared by the Zoo were from McNeel-based products (i.e.Rhino, Flamingo, Penguin, Brazil, and Bongo). With Zoo 5.0, third party Rhino plugin developers can now add support for their products to the Zoo.
  
 {{:developer:zoopluginaddlicense.png|}} {{:developer:zoopluginaddlicense.png|}}
Line 16: Line 16:
   * When a node shuts down, the license is returned to the Zoo's license pool.   * When a node shuts down, the license is returned to the Zoo's license pool.
  
-=====What is required to build a plug-in?===== +=====What is required to build a plugin?===== 
-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:+Zoo plugins are .NET Framework 4.0 assemblies. So, to create a plugin 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 freebut 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.]]+Also, all plugins 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.
  
 \\ \\