Thanks for the report. I've been very busy as of late with a number of tangential (or outright separate) developments and some conferences. Between the upcoming symposium in Manchester, my holiday, Siggraph and Acadia I won't be able to spend a lot of time on the forum. I'm logging all these bugs, but I don't know when I can get around to them.
-- David Rutten [email protected] Robert McNeel & Associates On May 3, 10:00 pm, Dimitrie <[email protected]> wrote: > ok so here's another bug for david :) > > c# scripting components don't reference the proper System.dll. maybe > we should get a bug tracker on... > > so to answer ineyeseekay's question, System.IO.Ports might already be > there, depending on whether you're using c# or vb.net scripting > components. > > @visose > i can imagine the pain to just add an unprintable polyline in .net > when compared to rhinoscript... heard that there's some work going on > in bridging this gap, can't wait for it to happen... > > glad to hear that automatic translations between c# and vb.net work > nice - i'm stuck to c# due to old habits but now it might seem that > publishing bi-lingual code is something to look forward to :)
