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:zoorhinoplugin [2020/11/25]
sandy [Creating Rhino C++ Plug-ins that use the Zoo]
developer:zoorhinoplugin [2020/11/25]
sandy [Requirements]
Line 4: Line 4:
  
 ===== Overview ===== ===== Overview =====
-Zoo 5.0 allows 3rd party plug-in developers to add licensing support for their products to the Zoo.+Zoo 5.0 allows 3rd party plugin developers to add licensing support for their products to the Zoo.
  
-The Rhino 5.0 C++ SDK allows developers to write plug-ins for Rhino that use the Rhino license manager and obtain licenses from Zoo servers.+The Rhino 5.0 C++ SDK allows developers to write plugins for Rhino that use the Rhino license manager and obtain licenses from Zoo servers.
  
  
 ===== Requirements ===== ===== Requirements =====
-Rhino C++ plug-ins are MFC dynamic link libraries. Thus, to create a plug-in for Rhino, you will need one of the following development tools:+Rhino C++ plugins are MFC dynamic link libraries. Thus, to create a plugin for Rhino, you will need one of the following development tools:
  
   - Microsoft Visual C++ 2005 (required for Rhino 5.0 32-bit)   - Microsoft Visual C++ 2005 (required for Rhino 5.0 32-bit)
   - Microsoft Visual C++ 2010 (required for Rhino 5.0 64-bit)   - Microsoft Visual C++ 2010 (required for Rhino 5.0 64-bit)
-  - [[http://wiki.mcneel.com/developer/sdksamples/rhino5wip|Rhino 5.0 C++ SDK]]+  - Rhino 5.0 C++ SDK
  
 Note, the Express Editions of Microsoft Visual Studio will **not** work, as they do not include MFC. Note, the Express Editions of Microsoft Visual Studio will **not** work, as they do not include MFC.
  
-Also, all Rhino plug-ins that use the Rhino license manager to access the Zoo must be signed with an Authenticode certificate issued by McNeel Plug-in 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 the following: +Also, all Rhino plugins that use the Rhino license manager to access the Zoo 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. 
- +
-[[developer:digital-signatures/create-request|Digitally Signing Plug-ins]]+
  
 ===== Creating a Rhino C++ Plug-in ===== ===== Creating a Rhino C++ Plug-in =====