Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

We replaced a dll in production (running on windows 2003) and it reset the application. I think that behavior is correct because anytime you replace a dll, it must read the changes on that first hit...

 

Is there something in 2003 to contradict this (that replacing a dll WILL NOT restart the app??) Has anyone come across it otherwise?

Posted
An alternative I've been playing with, and there are some post on this forum regarding it, is dynamically loading DLL's in another app domain, this way when a new one is loaded it can unload the original and load the new one without restarting. I haven't been able to perfect the process yet, but I've read that it is possible. Something to think about.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...