HighTechTalks DotNet Forums  

Updating assemblies at runtime

Dotnet Distributed Applications microsoft.public.dotnet.distributed_apps


Discuss Updating assemblies at runtime in the Dotnet Distributed Applications forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Sami Väisänen
 
Posts: n/a

Default Updating assemblies at runtime - 06-20-2006 , 04:10 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



Reply With Quote
  #2  
Old   
Michael Nemtsev
 
Posts: n/a

Default Re: Updating assemblies at runtime - 06-20-2006 , 04:25 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 Nietzsche



Reply With Quote
  #3  
Old   
Sami Väisänen
 
Posts: n/a

Default Re: Updating assemblies at runtime - 06-20-2006 , 04:38 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?



"Michael Nemtsev" <nemtsev (AT) msn (DOT) com> wrote

Quote:
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





Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.