Build error - bin folder

8 posts, 0 answers
  1. Mark
    Mark avatar
    20 posts
    Member since:
    Oct 2011

    Posted 02 Feb 2012 Link to this post

    ive recently installed the telerik tools in my site, but keep getting this error when i try and build the solution.

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "C:\Sites\MySite\bin\Telerik.Web.UI.xml". Access to the path 'C:\Sites\MySite\bin\Telerik.Web.UI.xml' is denied.

    i shut down VS and ensure the bin folder has read-only removed, but this error keeps coming back every time.

    how do i eradicate it ?
  2. Mira
    Mira avatar
    1124 posts

    Posted 07 Feb 2012 Link to this post


    Could you please try following this steps and let me know if the issue still persists
    1) Close the Visual Studio
    2) Stop the IIS if the site is deployed on it
    3) Close all other programs that eventually use “bin\Telerik.Web.UI.xml”
    These 3 steps are to ensure no one is locking the file for writing. Then, you can
    4) Check the security of “bin\Telerik.Web.UI.xml”, to make sure you have write permissions
    5) Now copy “...\Telerik.Web.UI.xml” to the “\bin” folder of your project.

    I hope this helps.

    the Telerik team
    Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>
  3. Andrew
    Andrew avatar
    5 posts
    Member since:
    Jan 2012

    Posted 05 Jun 2012 Link to this post

    Further to this, I've experienced this when trying a Rebuild in a Telerik MVC 3 Application on the Telerik.Web.Mvc.xml file.

    To solve, I've browsed to: C:\Program Files (x86)\Telerik\Extensions for ASP.NET MVC Q1 2012\Binaries\Mvc3 and added full control to my user account. This solves the issue.

    It seems that when the Telerik Extension copies the file to your project folder, your user account isn't given permission to delete the file when running a Rebuild.

  4. Joan
    Joan avatar
    44 posts
    Member since:
    Dec 2011

    Posted 04 Sep 2012 Link to this post

    This issue has now become more serious as it stops the compiler.  In prior releases it didn't.  It's not reasonable to stop IIS each time we compile and it doesn't solve the problem anyway.  The only way I've found so far to get around it is to "Clean" the project TWICE then compile it.
  5. Andrey
    Andrey avatar
    245 posts

    Posted 07 Sep 2012 Link to this post

    Hello Joan,

    Thank you for sharing your experience.

    This should not in any way be related to our assemblies, but is probably a deployment quirk of some kind. Could you share some additional details around your current deployment scheme and project setup? That way I, or possibly someone else from the community could give you a hint on how to get things working better on your side.

    All the best,
    the Telerik team
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
  6. Joan
    Joan avatar
    44 posts
    Member since:
    Dec 2011

    Posted 14 Oct 2012 Link to this post

    I think I know why the file is locked.  If I open the project and compile I don't have a problem.  I don't use the Casini web server, I use IIS.  If I run the site outside of Visual Studio, then IIS locks the file and the compiler has a problem with it.  The file is a 7MB documentation file that I don't think should be copied to the BIN folder at all.

    I think this would explain why some people have a problem and some don't.
  7. Rene
    Rene avatar
    65 posts
    Member since:
    Nov 2010

    Posted 13 Jan 2013 Link to this post

    It's non stop over here also - every build I get that error - and then have to rebuild a second item and them it works.

    Is there ANY way of stopping that automated file copy during building?
  8. Edward
    Edward avatar
    12 posts
    Member since:
    Oct 2009

    Posted 17 Jan 2013 Link to this post

    I'd suggest just switching over to using IIS Express or the Visual Studio Develiopment server for debugging. That should generally avoid any issues of the kind.

Back to Top