J
Jody L. Whitlock
Okay, I've banged my head against a wall for over a year now. Maybe
I'm just a rock when it comes to this.
I've got a new project, a Windows Service. The "application" itself is
in a DLL that is referenced by the exe. I did this for ease of
updating, just copy my new DLL(s) into an update directory and restart
the service when convienant. when the service EXE starts, it checks
for anything in my update dir, copies them over to the working dir,
then creates a new instance of the object inside my dll. This works
nicely, but I sat up last nite and wondered if I should explore loading
my DLL(s) into an appDomain of it's own, so when the service itself
finds a new DLL(s) in the update dir, it can just close the appDomain
the DLL(s) are in, then copy the junk over, and re-create the
appDomain. Nice and pretty.
There's one drawback, I have two event the DLL generates that my main
service captures and uses for varying reasons, so how to I proxy an
event across an appDomain???
I am friggin helpless in this matter for some odd reason.
JLW
--
I'm just a rock when it comes to this.
I've got a new project, a Windows Service. The "application" itself is
in a DLL that is referenced by the exe. I did this for ease of
updating, just copy my new DLL(s) into an update directory and restart
the service when convienant. when the service EXE starts, it checks
for anything in my update dir, copies them over to the working dir,
then creates a new instance of the object inside my dll. This works
nicely, but I sat up last nite and wondered if I should explore loading
my DLL(s) into an appDomain of it's own, so when the service itself
finds a new DLL(s) in the update dir, it can just close the appDomain
the DLL(s) are in, then copy the junk over, and re-create the
appDomain. Nice and pretty.
There's one drawback, I have two event the DLL generates that my main
service captures and uses for varying reasons, so how to I proxy an
event across an appDomain???
I am friggin helpless in this matter for some odd reason.
JLW
--