I think that's only the case for the C# component, in the VB component it looks like it's already loaded. I translated your qhull-gh connection to VB.net and no additional assemblies where required to be loaded.
Btw the automatic c# to vb translations work really well, i just had to fix i think 4 or 5 lines of code that where messed up. Now i'm manually 'translating' a rhinoscript to a vb.net component and its much harder :P On May 3, 8:14 pm, Dimitrie <didimit...@gmail.com> wrote: > I don't know if this will solve the problem, but i have stumbled a > while ago over something similar - System.Process wasn't around. > I managed to get what i wanted by custom-referencing the second > version of System.dll which you can probably find in something like C: > \WINDOWS\Microsoft.NET\Framework\v2.0.5[...]\ > relative to your windows folder... > > the component is going to turn orange but that's ok :) > > I just tested and it worked. > good luck! > > PS what are you going to use it for? sounds cool by the look of it - > external input devices hm...
