N
Nick Malik
My turn to ask a question
I am working on a plug-in for Sharepoint that will allow a developer to add
workflow rules. One of the rules will inform the adapter that it should
load a DLL that the developer writes, find a method that matches a
particular interface, and call it.
I know, in general, I should be looking at the reflection classes. Does
anyone have any design advice for me, or good working examples that would
serve as a foundation, so I'm not re-inventing the wheel?
Should I be loading the developer's DLL in a seperate App Domain? (My
environment: Sharepoint is an IIS application. It runs in its own
application pool on IIS6.) My code is already running in a protected
environment since I'm already using Sharepoint's plug-in architecture to
host my app.
Should I use attributes to find the intended DLL, or should I simply require
the developer to give me the name of the method to call?
I am working on a plug-in for Sharepoint that will allow a developer to add
workflow rules. One of the rules will inform the adapter that it should
load a DLL that the developer writes, find a method that matches a
particular interface, and call it.
I know, in general, I should be looking at the reflection classes. Does
anyone have any design advice for me, or good working examples that would
serve as a foundation, so I'm not re-inventing the wheel?
Should I be loading the developer's DLL in a seperate App Domain? (My
environment: Sharepoint is an IIS application. It runs in its own
application pool on IIS6.) My code is already running in a protected
environment since I'm already using Sharepoint's plug-in architecture to
host my app.
Should I use attributes to find the intended DLL, or should I simply require
the developer to give me the name of the method to call?