![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Hello Sami, You need to use AppDomainSetup.ShadowCopy* methods The idea is that: you assemblies is being copied and you app works with copies of you components, leaving original components untouched. Everything you can do is to create FileWatcher to look after you components, and when you replace them you app need to unload existed and use new (that will be shadow copied too) SV> Hello, SV> SV> I need to be able to add features to a running COM+ application. SV> This requires installing new versions of the assemblies. What would SV> be the best way to minimize the system downtime as this is mission SV> critical, or alternatively would there even exist a way to SV> completely do this without downtime or without having to replicate SV> the service? SV> SV> tia, SV> sami --- WBR, Michael Nemtsev :: blog: http://spaces.msn.com/laflour "At times one remains faithful to a cause only because its opponents do not cease to be insipid." (c) Friedrich Nietzsche |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |