Error Replacing DLL's

Results 1 to 4 of 4

Thread: Error Replacing DLL's

  1. #1
    Chong Chang Guest

    Default Error Replacing DLL's

    I have a web application and when attempting to overwrite some dll&#039;s in my /bin directory I get a message stating "There has been a sharing violation. The source or destination file may be in use".<BR><BR>According to the quickstart documentation, NO SERVER RESTART IS REQUIRED. However, I find this to be incorrect. I have to restart the server to allow me to overwrite the dll&#039;s. Anyone have any ideas?<BR><BR>Here&#039;s what the quickstart documentation states:<BR>======================================= ================<BR>No server restart required. When any part of an ASP.NET application is changed (for example, when a DLL in /bin is replaced), new requests immediately begin execution against the changed file or files. Currently executing requests are allowed to complete before the old application is gracefully torn down. The Web server does not require a restart when you change your application, even when replacing compiled code. <BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: Error Replacing DLL's

    Are these DLLs you are writing over DLLs that are .NET components? I.e., components created in a .NET-framework-friendly language (i.e., C#, VB.NET, etc.)?

  3. #3
    Jeff Nichols Guest

    Default RE: Error Replacing DLL's

    I&#039;m having a similar problem. I don&#039;t get an error when replacing the dll but the new code doesn&#039;t take effect. It seems to be cached in memory somewhere and my new version sitting in the /bin directory does not override it. If anyone knows how to clear this cache or has another way of using the newly compiled dll please let me know cause it&#039;s a real pain restarting IIS almost every time I make a change.

  4. #4
    Chong Chang Guest

    Default RE: Error Replacing DLL's

    Correct, these are what the quickstart guide terms as "Business Objects" which are .NET components used within my ASP.NET application.<BR><BR>I&#039;ve found a work-around for this problem. For some reason when you execute the ASP.NET application, the dlls&#039; archive flags are checked. You have to uncheck the archive property of the dlls for the system to allow you to over-write them. This work-around also works for the "Cannot copy..." error in VS.NET when attempting to re-compile a component.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts