just right click on the c# scripting component and select referenced assemblies. then just find the 2.0 version of System.dll from the .net framework. no syntax, since we can't write import statemets. But the referenced assembly thing does just that it adds an import statement on top of everything.
On May 5, 6:15 pm, np <[email protected]> wrote: > Yep its external devices. > > I've been working with them for Maya for a few years now and it seems > there's a good bit of demand for a grasshopper version. Also, if I > can get access to the .IO.PORTS dll it will be a really trivial thing > to accomplish. > Your workaround sounds like what I'm trying to do. What was the > syntax to do this? > > thanks for your help > > Nick > > On 3 May, 19:14, Dimitrie <[email protected]> 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...
