Visual Studio and .NET Framework Home
Large Numbers of WebSiteCache Files Slowing Visual Studio 2005 and Windows Performance
Anonymous THX 1138
as Not Reproducible
5/29/2008 8:19:23 AM
User(s) can reproduce this bug
We do development almost primarily with WinForms but have a small handful of web applications so developers have to install the Web Deployment add-on. Our problem is that developers are accumulating massive numbers of directories and files (24,000+ directories in one case) in the %userroot%\Local Settings\ApplicationData\Microsoft\WebSiteCache directory. Our solutions tend to have upward of 150-200 projects so this is a real problem. We are also seeing the following unnecessary lines (for windows apps!) in our .sln files that seem to be causing the issue:
ProjectSection(WebsiteProperties) = preProject
Debug.AspNetCompiler.Debug = "True"
Release.AspNetCompiler.Debug = "False"
Constantly deleting these lines from our .sln files or sweeping our WebSiteCache folder is not an acceptable solution to make our machines and Visual Studio 2005 performance faster. It was really hurting our productivity without even realizing what was happening. See some other posts out there as well:
All I would like is a way to turn this behavior on and off when needed (or just apply it to WEB projects not class libraries and the kitchen sink :-) ).
Visual Studio 2005 (All Products and Editions) Service Pack 1
Windows XP Professional
Operating System Language
Steps to Reproduce
Make a solution with hundreds of projects. Open and close it and check out the WebSiteCache folder above.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 12/22/2010 at 7:19 AM
Affects Windows 7 as well
on 12/22/2010 at 7:18 AM
When enough folders accumilate in the WebCache Folders, it cause chkdsk to fail to run correctly and it finds itself unable to read the security descriptor stream!!!
on 2/26/2009 at 9:39 AM
this bug was fixed in Visual Studio 2008.
Web Development Tools team.
on 5/29/2008 at 10:13 PM
Thanks for your feedback.
We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
© 2014 Microsoft