- rdnzl-devel@common-lisp.net - mailman3.common-lisp.net

[rdnzl-devel] New release 0.13.1 (Was: Could not load file or assembly error)
by Edi Weitz 22 Dec '09

22 Dec '09

I have now released a new version 0.13.1 which uses Load as a fallback (I had the same idea initially) and also exports do-rdnzl-collection. Raymond, thanks again for your help, but essentially this "fix" is against your original idea to catch errors early if an assembly isn't found, right? Do you have a better idea? (And good to hear about your experiences with RDNZL. I don't know of many users who deploy RDNZL "in earnest" - I'm certainly not one of them - but I'm always happy to hear about it.) Seth, thanks for the report. Cheers, Edi. On Tue, Dec 15, 2009 at 12:52 PM, Raymond Wiker <rwiker(a)gmail.com> wrote: > I just checked, and it does not appear that I used gacutil to register > rdnzl.dll. > > I tried running the messagebox example, using rdnzl 0.12.2 and 0.13. > 0.12.2 works, 0.13 does not. If I modify import.lisp so that > load-assembly uses the old code (with LoadWithPartialName), the > example works. Likewise if I change the code to try > LoadWithPartialName first, with Load (as used in 0.13) as a fallback. > The fallback probably won't help in the loading, but may be useful for > error trapping/reporting. > > Sorry about this - I will remember to test the demo programs as well > as my own code the next time... > > If you end up doing a new version instead of a rollback, it would be > good to have do-rdnzl-collection exported - it is implemented and > documented, but not exported (exactly as it was in the patch i sent, > so this, too, is my fault; again, sorry.) > > On a more positive note: I'm using rdnzl for feeding documents into a > search engine, and rdnzl works just great for me - good performance, > and no sign of any memory leaks - and also reasonably easy to get > working. Thanks again for allowing me to do (almost) Microsoft-free > programming under Windows :-) > > On Tue, Dec 15, 2009 at 11:51 AM, Raymond Wiker <rwiker(a)gmail.com> wrote: >> Could be due to the patch, but I think you may have to explicitly >> register rdnzl.ddl (using gacutil)? I seem to remember that I had to >> do that on Win7. I'll take a look on my Win7 installation. >> >> On Tue, Dec 15, 2009 at 8:03 AM, Edi Weitz <edi(a)agharta.de> wrote: >>> Hi Raymond, >>> >>> I think this is due to your recent patch. Isn't this supposed to work anymore? >>> >>> Thanks, >>> Edi. >>> >>> >>> On Tue, Dec 15, 2009 at 12:10 AM, Seth Burleigh <seth(a)tewebs.com> wrote: >>>> Im attempting to get this to work on windows 7. I have .net 3.5 installed >>>> but when I try this. >>>> >>>> >>>> >>>> (defpackage :rdnzl-test (:use :cl :rdnzl)) >>>> >>>> (in-package :rdnzl-test) >>>> >>>> >>>> >>>> (enable-rdnzl-syntax) >>>> >>>> (import-types "System.Windows.Forms" >>>> >>>> "MessageBox" "MessageBoxButtons" "DialogResult") >>>> >>>> >>>> >>>> >>>> >>>> I get the error >>>> >>>> .NET error (System.IO.FileNotFoundException): Could not load file or >>>> assembly 'System.Windows.Forms' or one of its dependencies. The system >>>> cannot find the file specified. >>>> >>>> >>>> >>>> Im pretty new to all of this, though im guessing this has something to do >>>> >>>> with setting environmental vars or something. But since you know the library >>>> >>>> I figure you’ll probably know the solution. >>>> >>>> >>>> >>>> Looking forward to getting this to work! Thanks! >>>> >>>> >>>> _______________________________________________ >>>> rdnzl-devel mailing list >>>> rdnzl-devel(a)common-lisp.net >>>> http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel >>>> >>>> >>> >> > >

2 1

[rdnzl-devel] Could not load file or assembly error
by Seth Burleigh 15 Dec '09

15 Dec '09

Im attempting to get this to work on windows 7. I have .net 3.5 installed but when I try this. (defpackage :rdnzl-test (:use :cl :rdnzl)) (in-package :rdnzl-test) (enable-rdnzl-syntax) (import-types "System.Windows.Forms" "MessageBox" "MessageBoxButtons" "DialogResult") I get the error .NET error (System.IO.FileNotFoundException): Could not load file or assembly 'System.Windows.Forms' or one of its dependencies. The system cannot find the file specified. Im pretty new to all of this, though im guessing this has something to do with setting environmental vars or something. But since you know the library I figure you'll probably know the solution. Looking forward to getting this to work! Thanks!

3 6

[rdnzl-devel] New release 0.13.0 (Was: LoadWithPartialName vs Load)
by Edi Weitz 12 Nov '09

12 Nov '09

Thanks Raymond, I've just made a new release. I made a few cosmetic changes, so please check if I didn't break anything. On Tue, Nov 10, 2009 at 11:55 AM, Raymond Wiker <rwiker(a)gmail.com> wrote: > I've had a little startup trouble with RDNZL, but this is mainly due to my > lack of familiarity with .NET. The use of Load instead of > LoadWithPartialName will most likely not be noticed by most people, but will > provide (IMO) more helpful behaviour in case of errors. It can also be > extended, at some later point, to use fully-qualified assembly names. > > The enclosed patch includes the trivial change to load-assembly, as well as > a new macro called do-rdnzl-container. do-rdnzl-container does for general > enumerable collections what do-rdnzl-arrays does for arrays. > > Thank you for making rdnzl available! > > > > > On Nov 9, 2009, at 22:16 , Edi Weitz wrote: > >> Hi Raymond, >> >> I have to admit that I rarely, if ever, used RDNZL myself. I started >> writing it for fun and only finished it because I gave a talk about >> it. At that time I was ambitious enough to bring it into a usable >> state, but as I didn't have any serious projects relying on it, I >> didn't keep track with .NET development and I'm sure it's out of tune >> now. >> >> If you have changes to make RDNZL better, I'm happy to accept patches, >> but I won't be able to test or evaluate them due to lack of time. >> I'll simply pack them into a new release if they follow the usual >> patch guidelines: >> >> http://weitz.de/patches.html >> >> Thanks, >> Edi. >> >> >> On Mon, Nov 9, 2009 at 9:36 AM, Raymond Wiker <rwiker(a)gmail.com> wrote: >>> >>> Hi, >>> I'm trying to use rdnzl to interface with certain .NET libraries. >>> These libraries have a callback mechanism that requires me to subclass >>> a C# class (or implement a C# interface) with two specific methods. I >>> haven't seen any mention that RDNZL can be used to subclass C# classes >>> (which I guess would be non-trivial to do), so I'm guessing that I >>> need to write a C# wrapper class for interfacing with Lisp. >>> >>> I'm having certain problems with this, probably caused by some .NET >>> details that I haven't (yet) understood. As part of unravelling this, >>> I've discovered that import-assembly calls load-assembly and that a >>> failure in load-assembly will cause a null assembly to be returned, >>> from which import-assembly will import exactly zero items. In other >>> words, any errors from load-assembly will not be signalled until >>> later. >>> >>> The MS documentation states that LoadWithPartialName (as used by >>> load-assembly) is an obsolete call, and that that >>> System.Reflection.Assembly.Load() should be used instead. Load() can >>> even be used with partial names, like this: >>> >>> (defun load-assembly-2 (name) >>> (let ((fullname (new "System.Reflection.AssemblyName"))) >>> (setf [%Name fullname] name) >>> [System.Reflection.Assembly.Load fullname])) >>> >>> I've just tried this, and load-assembly-2 gives an exception which is >>> transferred perfectly through RDNZL in cases where load-assembly >>> returns null. >>> >>> Regards, >>> Raymond Wiker >>> >>> _______________________________________________ >>> rdnzl-devel mailing list >>> rdnzl-devel(a)common-lisp.net >>> http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel >>> >>> >> >> _______________________________________________ >> rdnzl-devel mailing list >> rdnzl-devel(a)common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel > > >

1 0

[rdnzl-devel] LoadWithPartialName vs Load
by Raymond Wiker 10 Nov '09

10 Nov '09

Hi, I'm trying to use rdnzl to interface with certain .NET libraries. These libraries have a callback mechanism that requires me to subclass a C# class (or implement a C# interface) with two specific methods. I haven't seen any mention that RDNZL can be used to subclass C# classes (which I guess would be non-trivial to do), so I'm guessing that I need to write a C# wrapper class for interfacing with Lisp. I'm having certain problems with this, probably caused by some .NET details that I haven't (yet) understood. As part of unravelling this, I've discovered that import-assembly calls load-assembly and that a failure in load-assembly will cause a null assembly to be returned, from which import-assembly will import exactly zero items. In other words, any errors from load-assembly will not be signalled until later. The MS documentation states that LoadWithPartialName (as used by load-assembly) is an obsolete call, and that that System.Reflection.Assembly.Load() should be used instead. Load() can even be used with partial names, like this: (defun load-assembly-2 (name) (let ((fullname (new "System.Reflection.AssemblyName"))) (setf [%Name fullname] name) [System.Reflection.Assembly.Load fullname])) I've just tried this, and load-assembly-2 gives an exception which is transferred perfectly through RDNZL in cases where load-assembly returns null. Regards, Raymond Wiker

2 2

[rdnzl-devel] clisp threads and callbacks
by Matthew Swank 27 Aug '09

27 Aug '09

There is a rather cryptic comment on the RDNZL home page about CLisp having GC and callback issues because of lack of thread support. Is this because the host lisp's runtime data structures need to be protected from simultaneous access by threads created by RDNZL? I ask, because clisp now has limited multi-threading support on win32, and I would like to get it to work with RDNZL. Matt

2 1

[rdnzl-devel] RDNZL and (win32) Lispworks 64-bit
by Matthew Lamari 11 Aug '08

11 Aug '08

"Error: Could not register handle for external module :RDNZL:" I am investigating if RDNZL (and some other libs) can work viably in Lispworks 64 I'm inclined towards doing some footwork on this; but before investing any work I'd like to hear if it's something really trivial, or an absolute fool's errand. . . . Any thoughts? Thanks, Matt

2 1

[rdnzl-devel] A SVN repository for RDNZL on common-lisp.net, and some fixes
by Iver Odin Kvello 14 May '08

14 May '08

Following the case of the ambiguous property reference, Edi Weitz reanimated the RDNZL repository on common-lisp.net, and I've commited to it some fixes related to that issue, also making interop with COM a bit nicer. The repository is at svn://common-lisp.net/project/rdnzl/svn . The changes since the current release are 1. bugfixes for CAST, 2. An improvement to PROPERTY, resolving ambiguous property references by returning the value of the property defined in the most specific class, and 3. Extensions to PROPERTY and INVOKE so as to better handle COM objects with unknown type. Changes one and three were found by testing the Excel example after implementing change 2 and is mostly about an interesting feature of .Net interop where several basic methods in .Net reflection completely fail to work with COM objects - such as IsAssignable, GetProperty and GetMethod. This bites when an application returns a COM object without any interface information, done by for example Excel and others. Now, CAST had a bug in the testing of whether or not a cast was legal which hid this problem in the original Excel example; upon fixing this bug CAST had to be extended to explicitly handle COM objects using Marshal::GetComInterfaceForObject. The result should be that any COM object should be castable to any interface it supports. Even so, using PROPERTY on a COM object wouldn't neccessarily work, as forexample shown by the call in examples/excel.lisp: (cast [get_Item worksheets 1] "Worksheet") This thanks to GetProperty not being supported. According to random people on the internet, the way to get a property from a COM object using reflection, was to use InvokeMember and thus get the property using the IDispatch interface. I implemented this for properties and methods for 'unknown type' COM objects, and it actually works, except for the fact that since there is no way to get a PropertyInfo or MethodInfo using this, the type of the return-value will be uknown and thus probably a new __ComObject sans interface. But of course if all one needs to do is to use properties and call methods on the object, the interface or 'actual type' isn't actually neccessary. Thus, the example quoted from in excel.lisp can be reduced to: (defun get-excel-range (file-name range) (let* ((app (new "ApplicationClass")) (workbooks [%Workbooks app]) (workbook [Open workbooks file-name +missing+ nil +missing+ +missing+ +missing+ +missing+ +missing+ +missing+ +missing+ +missing+ +missing+ +missing+ +missing+ +missing+]) (worksheets [%Worksheets workbook]) (sheet [%Item worksheets 1]) (range [%Range sheet range +missing+])) (prog1 (cast [%Value2 [%Cells range]] "System.Array") [Quit app]))) - eliminating two casts and two 'direct' call to the get_-methods implementing a property. As for the ambigous properties this is handled by a straightforward search from most specific class upwards whenever the issue occurs, thus making RDNZL work like common sense and other systems like C#. To access a specific property given two of the same name, CASTing the object to the class defining the property in which you are interested works, like in C#. I think this would probably be worth testing for any users of COM Interop - it should remove a few sources of annoyance. Any comments or bugreports would be welcome. Iver

1 0

[rdnzl-devel] A bug in *setDotNetContainerType ( CAST)
by Iver Odin Kvello 25 Apr '08

25 Apr '08

I was working a bit on the 'ambiguous match'-thing for properties and ran into a weird thing using CAST, where I couldn't cast from a subclass to its super, both being quite vanilla. The problematic line is this from InvocationResult.cpp if (oldType->IsAssignableFrom(newType)) { I'm pretty sure this is supposed to be if (newType->IsAssignableFrom(oldType)) { This fixes the case I had problems with, but ufortunately reveals another problem in the Excel example, where now this no longer works: (cast [get_Item worksheets 1] "Worksheet") The object returned is a com-object returned as a System.Object, and the cast fails with "object must implement IConvertible". It's possible to cast the worksheet to System.__ComObject, but that doesn't help. This seemed to work earlier only because the first test was inverted, thus returning true in this case and forcing the container-type to the correct value. I'll try to find the source of this. The 'fix' for the ambiguos-match-thing, by the way, tries to simulate what C# does by searching the base classes of the object queried when the exception occured, thus letting one retrieve the 'other' property by casting to the appropriate superclass. That is, if one has classes A, B and C, with A > B > C, and A and B each defining a property with different return-type, then (property C) will return the one defined in B, whereas (property (cast C A)) will return the one defined in A. And that is how I found the issue with CAST. I put 'fix' in quotes because this is obviously not really neccessarily how things should work; C# is one thing but the .Net methods would more naturally just take the desired return-type as an argument where the property is ambiguous. But I think perhaps this is more intuitive (given C#'s behaviour), syntactically simpler, and also it seemed like good excercise. Regards, Iver

1 2

[rdnzl-devel] .NET error : Ambiguous match found.
by Matthew O'Connor 08 Apr '08

08 Apr '08

Hi All, I am getting a .NET error whilst simply trying to get access to the Controls property of a TableLayoutPanel in System.Windows.Forms. I have included a little test application below which demonstrates the issue. I am using Lispworks 5.0 and RDNZL 0.12.0. I am running Visual Studio 2008 so I think I've got version 3.5 of .NET. I've tried to have a look at it but don't understand enough about the ffi to come up with a possible cause. I did look at the System.Windows.Form assembly through the Visual Studio object viewer and I can't see any other definition of Controls. So I really can't see where the ambiguity would come from. Regards, Matthew ;; Bug ;; .NET error (System.Reflection.AmbiguousMatchException): Ambiguous match found. ;; NOTE - Make this point to your RDNZL implementation. (load "../RDNZL/rdnzl-0.12.0/load.lisp") (rdnzl:enable-rdnzl-syntax) (rdnzl:import-types "System.Windows.Forms" "TableLayoutPanel") (rdnzl:use-namespace "System.Windows.Forms") (setf tlp (rdnzl:new "TableLayoutPanel")) (rdnzl:property tlp "Controls")

2 7

[rdnzl-devel] Menus Experiment
by Matthew O Connor 27 Mar '08

27 Mar '08

Hi all, This time I have a little menus experiment. Again all you should have to do is change the path to RDNZL itself. Have fun! Regards, Matthew ;; ======================================================================== ;; Menus Experiment. ;; ;; Matthew O'Connor ;; ;; In this experiment I create some menus. I link the menus back to ;; callbacks when they are pressed and even control the state of the 'Save' ;; menu item by pressing the 'Save' or 'Save As' menu items. ;; ;; As usual there is no warranty. Use at your own peril. I am relatively ;; new to Lisp so you are warned. ;; NOTE: You need to modify this to point to the location of RDNZL on your system. (load "../RDNZL/rdnzl-0.12.0/load.lisp") (rdnzl:enable-rdnzl-syntax) (rdnzl:import-types "System.Windows.Forms" "Application" "Form" "MenuStrip" "ToolStripMenuItem" "ToolStripSeparator" "MessageBox" "MessageBoxButtons" "MessageBoxIcon") (rdnzl:use-namespace "System.Windows.Forms") ;; Display a message in a message box. (defun message(text &optional (caption "Message")) [MessageBox.Show text caption ;; we want the message box to have just the "OK" button [$MessageBoxButtons.OK] ;; We want an exclamation mark as the icon. [$MessageBoxIcon.Information]] nil) ;; Create a menu item and add it to the supplied menu strip. (defun create-menu (menu-strip-item x) (let ((menu (rdnzl:new "ToolStripMenuItem" (second x)))) ;; Bind the menu to the sybmol. (setf (symbol-value (first x)) menu) ;; Add the callback if one is supplied. (if (cddr x) [+Click menu (rdnzl:new "System.EventHandler" (car (cddr x)))]) (if (cdddr x) (setf [%Image menu] (rdnzl:property "Resources" (car (cdddr x))))) ;; Add the menu item to the parent. [Add [%DropDownItems menu-strip-item] menu])) ;; Create a menu splitter and add it to the supplied menu strip. (defun create-splitter (menu-strip-item) [Add [%DropDownItems menu-strip-item] (rdnzl:new "ToolStripSeparator")]) ;; Add either a menu item or a splitter to the supplied menu strip. (defun add-menus (menu-strip-item menus) (mapcar #'(lambda (x) (if (= (length x) 1) (create-splitter menu-strip-item) (create-menu menu-strip-item x))) menus)) ;; Build the menus. (defun build-menus (menu-strip menus) (mapcar #'(lambda (x) (let ((menu (rdnzl:new "ToolStripMenuItem" (second x)))) ;; Bind the menu to the symbol (setf (symbol-value (first x)) menu) ;; Take care of the children. (add-menus menu (third x)) ;; Add the menu to the MenuStrip. [Add [%Items menu-strip] menu])) menus)) ;; Callbacks. (defun file-new-clicked (object event) (message "file-new-clicked!!")) (defun file-open-clicked (object event) (message "file-open-clicked!!")) ;; Disable the Save menu item. (defun file-save-clicked (object event) (message "Disabling Save!") (setf [%Enabled menu-file-save] nil)) ;; Enable the Save menu item. (defun file-save-as-clicked (object event) (message "Enabling Save!") (setf [%Enabled menu-file-save] t)) ;; Exit the application (defun file-exit-clicked (object event) [Application.Exit]) (defun edit-undo-clicked (object event) (message "edit-undo-clicked!!")) (defun edit-redo-clicked (object event) (message "edit-redo-clicked!!")) ;; Create my experimental menu system. (defun create-menus (menu-strip) (setf menus '((menu-file "File" ((menu-file-new "New" file-new-clicked) (menu-file-open "Open" file-open-clicked) (menu-file-save "Save" file-save-clicked) (menu-file-save-as "Save As" file-save-as-clicked) (menu-file-splitter) (menu-file-exit "Exit" file-exit-clicked))) (menu-edit "Edit" ((menu-edit-undo "Undo" edit-undo-clicked) (menu-edit-redo "Redo" edit-redo-clicked))) (menu-help "Help"))) (build-menus menu-strip menus)) (defun run-menus-experiment () (let ((menu-strip (rdnzl:new "MenuStrip")) (form (rdnzl:new "Form"))) (setf [%Text form] "Menus Experiment") [Add [%Controls form] menu-strip] (create-menus menu-strip) [Application.Run form])) (run-menus-experiment) (rdnzl:disable-rdnzl-syntax)

1 0