Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How do you clear your Visual Studio cache on Windows Vista?

I have a problem where my ASP.NET controls are not able to be referenced from the code behind files.

I found a solution in Stack Overflow question ASP.NET controls cannot be referenced in code-behind in Visual Studio 2008.

But I cannot seem to find my Visual Studio cache to clear it. I am using Visual Studio 2005 on Windows Vista.

like image 666
Brian G Avatar asked Feb 06 '09 14:02

Brian G


People also ask

Where is the Visual Studio cache?

The Visual Studio component cache is located at %localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache.

Can I delete Visual Studio download cache?

YES you can delete this directory, if you have uninstalled Visual Studio.


2 Answers

The accepted answer gave two locations:

here

C:\Documents and Settings\Administrator\Local Settings\Temp\VWDWebCache

and possibly here

C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\WebsiteCache

Did you try those?

Edited to add

On my Windows Vista machine, it's located in

%Temp%\VWDWebCache 

and in

%LocalAppData%\Microsoft\WebsiteCache 

From your additional information (regarding team edition) this comes from Clear Client TFS Cache:

Clear Client TFS Cache

Visual Studio and Team Explorer provide a caching mechanism which can get out of sync. If I have multiple instances of a single TFS which can be connected to from a single Visual Studio client, that client can become confused.

To solve it..

For Windows Vista delete contents of this folder

%LocalAppData%\Microsoft\Team Foundation\1.0\Cache

like image 70
GregD Avatar answered Sep 20 '22 02:09

GregD


I experienced this today. The value in Config was the updated one but the application would return the older value, stop and starting the solution did nothing.

So I cleared the .Net Temp folder.

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files 

It shouldn't create bugs but to be safe close your solution down first. Clear the Temporary ASP.NET Files then load up your solution.

My issue was sorted.

like image 24
Adam Avatar answered Sep 19 '22 02:09

Adam