Stop Bin folder creating .dll copies

Last post 06-27-2007 6:03 PM by Andy_yzf. 2 replies.

Sort Posts:

  • Stop Bin folder creating .dll copies

    06-27-2007, 12:28 AM
    • Member
      6 point Member
    • Andy_yzf
    • Member since 05-28-2007, 6:22 PM
    • Posts 17

    Hi there, I updated my control toolkit with the latest version.  Went into site to continue working, when adding a new AJAX control onto the page was prompted (something like) "Do you want to copy .dll...." - foolishly selected yes.  As a result, I now have heaps of copies of the same AjaxControlToolkit.resources.dll, each in separate folders named AR, CS, DE etc.  Tried deleting the folders but they keep getting rebuilt....frustrating!!  Anyone know how to stop this from happening, thanks, Andy

  • Re: Stop Bin folder creating .dll copies

    06-27-2007, 3:23 PM
    Answer
    • Contributor
      2,610 point Contributor
    • kirtid
    • Member since 11-18-2006, 12:41 AM
    • Redmond
    • Posts 658

    If you are using the no-source version of the Toolkit it includes a "Release" dll and this behavior is by default. However, with the source version a debug Toolkit dll is built by default and for development purposes you can reference that. It will not create the resource assemblies and your development process will be faster. If you do not want to go through all this you can always delete the language dlls that you don't care about and continue with your work.

    Kirti Deshpande
    Program Manager, Silverlight and ASP.NET AJAX
    Microsoft

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Re: Stop Bin folder creating .dll copies

    06-27-2007, 6:03 PM
    • Member
      6 point Member
    • Andy_yzf
    • Member since 05-28-2007, 6:22 PM
    • Posts 17

    Thanks for that - the problem was that I had followed the video in moving the toolkit .dll to the binaries folder and referencing that.  When I updated this, I did not follow the steps of copying out the .dll and referencing it - instead VWD referenced the Bin directory of the latest copy of the Source Toolkit Sample website (which includes a number of folders with .dlls).

    SO - just repeated the initial steps by removing the old toolbar and rebuilding it, then clicking on the toolkit .dll in the bin directory of the project and changing its reference to the Binaries folder where I copied the Toolkit .dll and hey presto!  Problem solved.

Page 1 of 1 (3 items)