This article should cover all aspects of clearing the cache in Visual WebGui application scenarios, as well as describing the different levels of cache, and how to clear each.

Special mention should be for the Disable Caching switch in web.config, and what effect it has. PrivateVersion should also be discussed/referenced.

The need to rereference Gizmox DLL's after version change should also be discussed (remember different folder locations for DLL's based on with or without sources installations).

This procedure for clearing the cache, has been posted countless times on the forums. It deserves some overhaul and update, but stands here until this article is fully written.

• Shut down VS if it's running
• Delete your browser cache (IE=Delete temporary internet files FF=Clear Private Data + Cache)
• Shut down all running Microsoft Web-Servers on your machine, including MS Visual Studio Web-Servers.
• Go to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.xxxxx\Temporary ASP.NET Files, delete all Visual WebGui assemblies (Gizmox.WebGUI.*.dll). Please note that this step removes server cache for both MS Visual Studio Web-Servers and MS IIS. (Note that for Vista/Win7 and Visual Studio Development server this directory might be different and you should then look for it at 'c:\users\<username>i\AppData\local\temp\Temporary ASP.NET Files' )
  
• Open sample application in MS Visual Studio.
• Delete obj and bin folders (and ClientBin if SilverLight deploy)
• [For Visual Studio 2005 only] Delete all Gizmox references
• [For Visual Studio 2005 only] Reference the Gixmox DLL's, which now should be correct version
• Temporarily set "Disable Caching" in General tab of Visual WebGui integration (remember setting back if production app). This is equivialent to Web.config setting: <add name="VWG_DisableCachingSwitch" value="1" />
• Increase Private Version of project
• Clean
• Recompile
• If you have a "route" directory in the root directory of your project (generated from use of StaticResources), remove it completely.
  

After clearing the cache on your development machine and deployed your application to the webserver, making sure that all required DLLs are up to date on the webserver, these are the extra steps needed to completely clear cache on the dedicated webserver:

• Shut down IIS if it's running. This is an extream step and is not always doable. If not doable, you might be unable to delete some locked files in later steps.
• Go to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.xxxxx\Temporary ASP.NET Files, delete all Visual WebGui assemblies (Gizmox.WebGUI.*.dll).
  
• Increase Private Version of project by updating web.config
  
• If you have a "route" directory in the root directory of your project (generated from use of StaticResources), remove it completely.
  
• Start IIS, if it was stopped in step 1

On ordinary browser clients there is only one step to perform.

• Delete browser cache (IE=Delete temporary internet files FF=Clear Private Data + Cache)
  

• CCleaner tool for clearing browser(s) cache (and more)