Such procedure might sound plausible at first, but soon get tedious when a lot of small changes needs to be performed on the same plug-in for a lot of times. The naive way, then, for one who is developing their own plug-in for deploying it, is to manually copy the generated plug-in after building it to this location and restart Rhino. Rhino and Grasshopper (Which runs in the background even when one closes the Grasshopper window) will load the newly developed plug-in at the next restart of the main Rhino software. Such folder can be found by going to Grasshopper Window - File - Special Folders - Component Folders,Ĭ:\Users\YOUR_USER_NAME\AppData\Roaming\Grasshopper\Libraries However, in order for Rhino to correctly recognize the custom plug-in we wrote and load it so we can see it in Grasshopper shelf, the plug-in should be placed inside a special folder. Rhino’s Default Nature of Loading a GH Plug-In \M圜omponent\bin\M圜omponent.gha for older versions of Rhino. \M圜omponent\bin\Debug\net48\M圜omponent.gha, where the net48 can vary, and such file might exist in. The default nature of building a Grasshopper component using a solution (In this post, I will refer to this solution as M圜omponent.sln) in Visual Studio is that it generates a M圜omponent.gha file under the project local folder. Automating Grasshopper plugin deployment Visual Studio’s Default Nature of Building a GH Plug-In This post was written based on Visual Studio 2019, Windows 11, and Rhino 7, at the time of writing. This post is essentially some notes I jogged down from Long Nguyen’s C# Scripting and Plugin Development for Grasshopper,Īs it is very helpful when setting up build environment for Rhino using Visual Studio. Automatic plugin deployment for Rhino and Grasshopper using Visual Studio.
0 Comments
Leave a Reply. |