Grasshopper

algorithmic modeling for Rhino

I have done something horribly wrong.  I wrote an RHP that attempts to use GH_SettingsServer to store and refresh certain values.  In order to pull this off, I renamed Grasshopper.dll and GH_IO.dll and referenced them in my project.  I then packaged it all up in an installer that deploys the RHP and dlls to the plug-ins folder and registers the plugin in the Registry.

Everything works great except for one small detail.  After the installation, existing installations of Grasshopper are pretty much destroyed.  All of the non-plugin components come up missing.  A reinstall of Grasshopper fixed the problem, but obviously I want to avoid the problem in the first place.

Any thoughts?

Marc

Views: 301

Replies to This Discussion

Yeah renaming and copying around assemblies is not a good idea. You may be able to hack together a way to make this work, but it'll be more work and more dangerous than just writing a settings implementation of your own.

I knew a slap on the wrist was coming.  :)

In the meantime, we did what you suggested, and implemented our own settings server, using yours as a model.  Working great.  Thanks!

Marc

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service