custom component

Replies to This Discussion

Permalink Reply by Steve Lewis on April 26, 2010 at 1:19pm

Is the dll in the develop settings folder specified when rhinocommand _developsettings entered in Rhino.

Permalink Reply by to] on April 26, 2010 at 1:33pm

solved.... *.dll has to be in the grasshopper folder
strange but all other places do not work ... think their is a override

Permalink Reply by Luis Fraguada on April 26, 2010 at 1:54pm

Looking forward to this!

Permalink Reply by to] on April 27, 2010 at 4:42am

if you have a wish or idea let me know.....

Permalink Reply by David Rutten on April 26, 2010 at 1:56pm

This is a bug in Grasshopper. Or rather, I should be smarter about handling dll requests.

If you disable the COFF loading in _GrasshopperDeveloperSetting, does it work then?

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Ben Sitler on April 26, 2010 at 2:15pm

haha, to], you're a genius about placing the .dll in the proper place. I was using COM as well..David this fixes my problem as well!

Best regards,
Ben

Permalink Reply by Giulio Piacentino on April 26, 2010 at 2:19pm

Hi Thomas,

if this happens, it might mean that the .dll is not installed in the GAC. Because of administrator rights, you cannot generally put it in there yourself from Grasshopper.

This is how you could bypass this problem and make the runtime find and load that .dll even if you cannot/do not want to distribute NDde.dll.

- In the component static constructor, handle the AssemblyResolve event: AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(HelpResolveDll);
where HelpResolveDll is a static method that checks that the runtime is really looking for that .dll ("NDde.dll, Version=..."), then loads it with Assembly.LoadFrom(fullPath). fullPath is the full path where you know for sure that the .dll is located. Do you know this in general?

- In your code, defer the loading of NDde.dll to the SolveInstance() part (this is accomplished by not referencing any type in that .dll in other methods).

I know this is a bit of extra coding, but it works.
I hope this is helpful,

- Giulio

Permalink Reply by Jon Mirtschin on May 14, 2010 at 12:40am

Hey Giulio, hope you're well.

Thanks for posting this, I interact with my rhino plug-in assembly from the Grasshopper assembly, and it seems I need to use this technique for v0.7 as simply duplicating the dll in the Grasshopper components folder would load a new instance of the assembly rather than the existing..

Cheers,

Jon