Skip to content

Getting started for developers

Welcome Developers! 🚀

Here's a quick start guide. After reading this, you might want to head to create your own Toolkit.

Building BHoM from Source

Please follow the steps below:

  1. Use git clone (or use GitHub desktop) to download the repositories in the list below.
  2. Use your preferred IDE to build the solutions in the order as they appear below. We recommend Visual Studio Community.

Build order

The first time you build BHoM you need to clone and build the repos in the order specified below.

You must pick all the Mandatory repos.

Rebuilding and seeing changes in the UIs (Grasshopper/Dynamo/Excel)

When building in visual studio, the compiled assemblies will go in the ./Build folder of your Repo; additionally, there is a Post-Build event that copies the files in the central BHoM folder: C:\ProgramData\BHoM\Assemblies.

When you build, if there is any UI open (e.g. Rhino/Grasshopper/Revit/Excel), the dlls will not be overwritten in the central folder because they are referenced by the UI software. Therefore, to ensure the changes are visible in the UI, you must make sure to close all UI software, then reopen it to see updated changes.

Tip

When developing a Toolkit, in order to reduce rebuild iterations, you might want to:

  1. Rebuild your Toolkit
  2. Rebuild BHoM_UI
  3. Start Debugging your Toolkit with an UI application attached.

The last step will fire up your UI application and you will be able to modify the code while debugging, on-the-fly (just press the Pause button in Visual Studio).

Note that not all IDEs support this (notably, not the Express editions of Visual Studio – only the Community, Professional and Enterprise ones do).

An alternative that always works is, after steps 1 and 2 above, simply fire up your UI application and attach to its process. This way you will be able to follow code execution and check exceptions; however, this does not allow for code modification while debugging.

Mandatory base repos

Main repos

Compile each of these, one after the other:

User interface(s)

Compile one or more of the following - depending on the User interface software you want to use:

  1. Rhinoceros_Toolkit and then Grasshopper_Toolkit (requires Rhinoceros_Toolkit)
  2. Excel_Toolkit
  3. Dynamo_Toolkit

The following repos are optional.

Optional base repos

These repos are sometimes used as stand-alone, and sometimes are also referenced by other repos.

You might find them useful 🚀

  • BHoM_Datasets - makes Datasets available (some test scripts might be using them)
  • Socket_Toolkit - send messages through Sockets. Some toolkits use this.
  • Mongo_Toolkit - database connection. Some toolkits use this.
  • Versioning_Toolkit - allows retro-compatibility of components (auto upgrade to newest version).

Toolkits 🌍

Toolkits provide the connection to other software.

Clone and build any toolkit you want to use!

Some examples:

FAQ and help

I can't Rebuild the solution: NuGet package(s) missing error

Sometimes you might encounter this error. Although Visual Studio "Rebuild All" command should take care of Restoring the NuGet packages for you, to solve this just run that manually.
Right click the solution → Restore NuGet Packages.

I have done some changes to my code, but when I open Grasshopper (or Dynamo, or Excel) the code still behaves as before! Why it is not updated?

After compiling, check that the Build was successful, by looking in the "Output" tab at the bottom of the VS interface; make sure no errors are there, and also that the Post-build event worked successfully. See the notes above.


Last update: March 17, 2023