Are you using IIS as the "host EXE", or something that you wrote?
If you have multiple EXEs, you'll need to talk to each over its own port. That might cause firewall issues and so on. Otherwise it seems to make good sense to me (even though you could use separate AppDomains). It is unfortunate that there is no general "unload a particular DLL" mechanisms in many tools (like IIS) that load DLLs on demand. At 03:27 AM 12/9/2004, Diranieh, Yazan wrote >We have a client/server .NET distributed application with server-side >components currently implemented as DLLs and running within a single process >on the server. Clients talk with these server-side components via .NET >Remoting. > >The current thinking is to convert major server-side DLLs into outright >server-side EXEs. Rational being: > >1. Improved reliability by isolating components within their own process >boundary. >2. Improved manageability by giving each EXE its own config file. Managing a >single config file for many DLLs is becoming error-prone. >3. With the DLL-approach, you'd have to stop the host exe to update a DLL, >whereas with EXE, you only need to stop a single EXE. > >On the down side: >1. Because communication between server-side components themselves is minimal >and sometimes non-existent, the issue of performance due to EXEs communicating >with each other does not weigh much. >2. Increased manageability, but we've already implemented a simple GUI to >stop/start individual server-side EXEs in case of a crash. > >Does anybody have serious issues with this approach where logically-isolated >server-side DLLs are converted into server-side EXEs? > >Yazan.Diranieh - 0 error(s), 0 warning(s) >www.diranieh.com J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with C# November 29 - December 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
