I have an .exe application which calls into various plug-in DLLs. It
provides an instance of a class within the .exe so that the plug-ins can
query properties from the application and invoke methods upon it.
In VB.NET I am unable to early-bind to this object as I can't reference the
..exe. Instead I have to either late-bind (which I'd really rather not do) or
move my classes to a separate .DLL, which will fragment my application.
I have an .exe application which calls into various plug-in DLLs. It
provides an instance of a class within the .exe so that the plug-ins can
query properties from the application and invoke methods upon it.
In VB.NET I am unable to early-bind to this object as I can't reference
the .exe. Instead I have to either late-bind (which I'd really rather not
do) or move my classes to a separate .DLL, which will fragment my
application.
I presume the Exe will be treated as a library of types rather than an
executable. What I mean is, CLR may not 'run' the referenced exe but allow
us to create instances of types within the referenced exe.
I presume the Exe will be treated as a library of types rather than an
executable. What I mean is, CLR may not 'run' the referenced exe but allow
us to create instances of types within the referenced exe.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.