Hi Michele, If - you are running IIS 6 - and not using sessions - or store sessions into a state server or database,
then you can follow the next scenario, without any of your users noticing you updated the dll. - rename the old dll - now you can place the new dll next to it - in iis6, recycle the application pool that runs your web app - new requests will pick up the new dll - at a certain time you can delete the old dll (after the (old) aspnet worker process has ended). HTH // Ryan On 9/1/05, Michele Lepri <[EMAIL PROTECTED]> wrote: > Hi list! > > I'm a new user. > My name is Michele Lepri. > > The appDomain is a simple asp.net application. > > When I quit the appdomain (with the usual methods), seems to look that the > file's lock on the native dll (not assembly!), bind by some [DllImport(..)] > attributes, not being released. > > Also the assembly that has the methods with [DllImport(..)] attributes, > appear to be locks. > > The only mode to release the lock, is to kill the aspnet work process.. > The problem is that I can't do that on the production machine: I can't > update native dll.. > > What I can do? > > Sorry for my not well English :) > > Bye! > > Michele Lepri > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
