DotNet Visual Lisp

[dmarcotte4]

I would like to see the DotNet support interaction with Visual Lisp. It would make the transition a go little easier for us lispers

Daniel

[scottden]

I think I would rather see autocad support .NET fully. Maybe even VBA.NET?

[ntaylor]

I think I would rather see autocad support .NET fully. Maybe even VBA.NET? Visual Studio Tools for Applications is the .NET equivalent of VBA and provides both VB & C# syntax. Personally I think if lispers want to use the .NET API they should learn VB or C#. I think Autodesk should focus effort on improving the .NET API and developing comprehensive documentation independent of the ObjectARX documentation.

Regards - Nathan

[dmarcotte4]

Let me clarify, I think the .NET API should be able to interact with visual lisp the way ObjectARX can. I.e. like acedDefun() calls. If I can build one function at a time using C#, it would make porting lisp applications much easier.

[irneb]

Should be no reason anymore for not having this. .NET is even already available in CommonLisp (although the extension won't work as-is in AutoLisp). See this (http://www.weitz.de/rdnzl/).

Unfortunately AutoLisp is quite far removed from CommonLisp after 20+ years of seperate development. Not to mention that ADesk only used a portion of LISP to begin with when they created their ALisp interpreter.

But as can shown by this extension, it should not be that difficult to implement even in ALisp / VLisp. Basically just a form of interface to the .NET libraries. Very much the same as the VLisp's vlax mehods which interface with the COM / ActiveX libraries.