Installing Tools (Windows)
This guide covers all the necessary tools required to author custom Grasshopper components on Windows.
By the end of this guide, you should have all the tools installed necessary for authoring, building, and debugging custom Grasshopper components in Rhino for Windows.
This guide presumes you have an:
- A PC running Microsoft Windows 7 or later.
- Rhino 6 for Windows
Install Visual Studio
Visual Studio is Microsoft’s flagship development platform and Integrated Development Environment (IDE). Visual Studio now comes in three major “streams”: Visual Studio Code1, Visual Studio Online2, and Visual Studio “proper”3. In order to author custom Grasshopper components, you will need Visual Studio “proper” (Visual Studio Code and Visual Studio Online are not supported).
At the time of this writing, Visual Studio “proper” comes in three editions: Community, Professional, and Enterprise. Any of these editions will work. Additionally, Visual Studio Express 2015 for Windows Desktop will work with more limited debugging support4. Other Express versions, such as Express for Windows, Express for Web or Team Foundation Server 2015 Express, will not work.
NOTE: Grasshopper components can be authored in Visual Studio 2010, 2012, 2013, 2015, and 2017 both in C# and VB, and included in Ultimate, Professional, Premium, C# Express, Vb Express and Windows Desktop Express (where available). For the purposes of this guide, we will presume you are using Visual Studio Community Edition.
- Visual Studio 2017 Community Edition is free from Microsoft for students, open-source contributors, and small teams. Details here. Click the Community button to download the installer.
- Run the Visual Studio installer you downloaded from Microsoft, in this case vs_community.exe.
- Follow the onscreen prompts to install Visual Studio. It is recommended that you install the Typical installation. Depending on your internet connection, this can take minutes or hours. When successfully installed, click the Launch button.
The Grasshopper Assembly templates contains wizards to get you started creating components quickly.
- Launch Visual Studio.
- Navigate to Tools > Extensions and Updates…
- In the left-hand sidebar, expand the Online section, then select the Visual Studio Gallery entry…
- In the Search field, search for Grasshopper. This filters the gallery list below.
- Find Grasshopper Assembly for v6 and select it.
- Click the Download button. The extension installation should begin.
- You must Accept the license agreement by clicking on the Install button.
- If the installation is successful, you will be redirected to this developer website and the extension should appear in your list of Installed extensions.
Congratulations! You have the tools to build custom Grasshopper components for Grasshopper for Windows. Now what?
Check out the Your First Component (Windows) guide for instructions building - your guessed it - your first component.
Visual Studio Code is Microsoft’s cross-platform source code editor for Windows, Linux, and macOS. At the time of this writing, Visual Studio code does not yet support the features required to author Grasshopper components ↩
Visual Studio Online is Microsoft’s online counterpart to the desktop edition of Visual Studio (referred to as Visual Studio “proper” above). We have not tested using Visual Studio Online to debug Grasshopper components as having a copy of Rhino and Grasshopper running would prove logistically difficult. ↩
Visual Studio “proper” is the desktop version of Visual Studio…we are only attaching the “proper” epithet to distinguish it from the Visual Studio Code and Visual Studio Online. In subsequent guides this will be referred to as simply “Visual Studio.” ↩
Visual Studio 2017 Community Edition offers a development platform that has a less strict licensing agreement policy than the Community edition. Please refer to the EULA for complete details, available during installation. In this edition, debugging of Rhino and Grasshopper can be started, but the location of the Rhino executable (rhino.exe), usually available in the Project property page, in the Debug tab, cannot be changed in the UI. After Wizard completion, the location of the Rhino executable can only be edited in the XML of the resulting .csproj file, in the main folder of the solution. ↩