Create DCOM application from within .Net environment: Part V

It could be consumed by both managed and unmanaged client but there are a couple of advises that I could provide in this context, is in fact, if a DCOM is leveraged by .Net then it is worth to use .Net remoting if you will consume the DCOM from a .Net client, you tell me why should I use .Net over the DCOM protocol, it simply because it id not supported by .Net client application and all DCOM objects are derived from the ServicedComponent class that inherit it self the famous MarshalByRefObject class, the main used class in a .Net remoting context Other thing that could be said, in certain condition that happened to me and I don't know if you have already encountred this situation, the Visual Studio is not able to recompile or update the component when it is modified during the developement cycle. It dues to the dllhost assembly to prevent that from happening you have to kill the dllhost.exe relative process

Please don't forget to give you rate

First I recompiled the component project and it was updated on my development machine on condition that no application was consuming it that moment. My problem is: i need to consume it by non managed clients and if possible without installing .NET framework on every client machine (only on the server). Another issue was config file, that is not loaded by a library and must be forced to load (like ConfigurationManager.OpenExeConfiguration(...) or any suitable IO class).