I have tested your code but I get errors.
Which versions of visual studio/VB.NET and framework are you using?
Also note that this is the old EntryPoint:="dllEvalStr".
The new is EntryPoint:="newlispEvalStr"
DLL does not work from VBA
Erich,
I have got your sample code and only start 'NewLispDotNet.exe' from the bin-folder. I get the sample form and type '(setq a 5)' and hit 'Evaluate'. Then I hit it a second and a third time. First and second return 5. With the third hit I get:
System.NullReferenceException: Der Objektverweiss wurde nicht auf eine Objektinstanz festgelegt.
at NewLispDotNet.Form1.dllNewlispeval(String txt)
...
...
Then I compiled the latest 8.2.0 source to a BCC-DLL and replace the GCC-DLL with it. Then I could use your VB.NET sample without problem.
I have got your sample code and only start 'NewLispDotNet.exe' from the bin-folder. I get the sample form and type '(setq a 5)' and hit 'Evaluate'. Then I hit it a second and a third time. First and second return 5. With the third hit I get:
System.NullReferenceException: Der Objektverweiss wurde nicht auf eine Objektinstanz festgelegt.
at NewLispDotNet.Form1.dllNewlispeval(String txt)
...
...
Then I compiled the latest 8.2.0 source to a BCC-DLL and replace the GCC-DLL with it. Then I could use your VB.NET sample without problem.
Hans-Peter
In current:
http://www.newlisp.org/code/NewLispDotNet.zip
in Module1.vb is the deprecated 'dllEvalStr' used instead of 'newlispEvalStr'.
Not yet a problem but maybe in the future.
http://www.newlisp.org/code/NewLispDotNet.zip
in Module1.vb is the deprecated 'dllEvalStr' used instead of 'newlispEvalStr'.
Not yet a problem but maybe in the future.
Hans-Peter