Groups | Blog | Home
all groups > dotnet distributed apps > june 2006 >

dotnet distributed apps : Updating assemblies at runtime



Michael Nemtsev
6/20/2006 8:25:11 PM
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 Nietzsch

Sami Väisänen
6/20/2006 11:10:57 PM
Hello,

I need to be able to add features to a running COM+ application. This
requires installing new versions of the assemblies. What would be the best
way to minimize the system downtime as this is mission critical, or
alternatively would there even exist a way to completely do this without
downtime or without having to replicate the service?

tia,
sami

Sami Väisänen
6/20/2006 11:38:18 PM
Thanks for you reply.

I can see that this helps with being able to update the assemblies on the
system, but how can i propagate the changes into the running COM+
applications as well, or then alternatively automate the update operation
without causing a long interruption to the clients?



[quoted text, click to view]

AddThis Social Bookmark Button