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
developer:sdksamples:manualsdkdifferences [2016/04/08]
sandy
developer:sdksamples:manualsdkdifferences [2016/04/08] (current)
sandy
Line 9: Line 9:
 It really depends on which programming language you are proficient at and what you are trying to do. It really depends on which programming language you are proficient at and what you are trying to do.
  
-If you are a C++ developer, or you have a large C++ application that you would like to convert into a Rhino plug-in, you should probably ​be using the standard C++ SDK.+If you are a C++ developer, or you have a large C++ application that you would like to convert into a Rhino plug-in, you should probably ​use the standard C++ SDK.
  
 If you are thinking of using Rhino.NET instead of the standard C++ SDK, here are some disadvantages and advantages to choosing Rhino.NET over the standard C++ SDK. If you are thinking of using Rhino.NET instead of the standard C++ SDK, here are some disadvantages and advantages to choosing Rhino.NET over the standard C++ SDK.
Line 20: Line 20:
 =====Advantages to choosing Rhino.NET===== =====Advantages to choosing Rhino.NET=====
  
-  * Free compiler. The C++ SDK requires a version of Visual Studio that must be purchased ​from Microsoft, ​where plug-ins for the Rhino.NET SDK can be created ​with the free Visual Studio Express Editions. This is great for people who want to try out plug-in development.+  * Free compiler. The C++ SDK requires a version of Visual Studio that you must purchase ​from Microsoft. On the other handyou can create ​plug-ins for the Rhino.NET SDK with the free Visual Studio Express Editions. This is great for people who want to try out plug-in development.
   * Familiarity. If you already know VB.NET or C#, it isn’t as big of a jump as learning a new language (C++) and learning a large SDK.   * Familiarity. If you already know VB.NET or C#, it isn’t as big of a jump as learning a new language (C++) and learning a large SDK.
   * Similar to C++ SDK. The classes and functions in Rhino.NET have extremely similar names and functionality. This means that if you get to a point where you need to convert your Rhino.NET plug-in to a C++ plug-in, you should be able to easily translate your .NET code to C++ within a short period of time.   * Similar to C++ SDK. The classes and functions in Rhino.NET have extremely similar names and functionality. This means that if you get to a point where you need to convert your Rhino.NET plug-in to a C++ plug-in, you should be able to easily translate your .NET code to C++ within a short period of time.
developer/sdksamples/manualsdkdifferences.txt · Last modified: 2016/04/08 by sandy