@MohamedAbed would you be so nice and give me more details?
–
RookianSep 26 '11 at 12:31

1

In order for any framework, IoC container, or code by hand, to support replacing assembly at run time would either: - Load these assemblies each in a separate app domain in order to be able to unload an assembly and load another instead (replace) .. this will lead to a performance and memory footpring implication because having separate appdomains has it's cost of marshaling and memory management. - Replace the content of the assembly at run time in the IL level (interception) and that also will have huge cost in pefrormance.
–
Mohamed AbedSep 26 '11 at 12:52

this sounds interesting. As Mohamed Abed mentioned in his comment this would lead to a peformance and memory footpring implication. So is this a relevant or irrelevant performance issue?
–
RookianSep 27 '11 at 14:26

In the scenario of a web application using IIS. 2nd question would be: How can I build this "magic" in non webapplications and what issues can I encounter?
–
RookianSep 27 '11 at 14:59

1

Well, you don't update the DLL's often so I don't see any performance penalties. imho the same problem doesn't exist for client applications. Simply restart the application after updating the DLLs
–
jgauffinSep 27 '11 at 16:22

What if I cant easily close my application, because it has to be run everytime. So what I still want to achieve is to replace an assembly(dll) at runtime. As I have understood you, there should be no problem.
–
RookianSep 27 '11 at 20:43