Clean out vswebcache

By Don Kiely

January 2003 issue

Technology toolbox: ASP. NET

Level: Intermediate

I F you spelunk around your asp. net Development machine-particularly if you're a conscientious geek who monitors and cleans out your clients and settings directory regularly-you 've probably found something such as C: \ Documents and Settings \ username \ vswebcache. you'll find subdirectories in it named for each server on which you 've ve worked on an ASP. net app while using this machine. in each of those subdirectories, You'll find other subdirectories for each project, along with other detritus. if you work with ASP. net a lot, you're likely to find your megabytes of miscellaneous files, hundreds of other subdirectories, and plenty of embarrassing junk from your first efforts writing. net code you thought you 'd long since cleaned off your machine. i'll explain what vswebcache is, why all that junk is there, and whether it's safe to blow it away.

vswebcache's primary purpose is to support offline development. suppose you're developing an app that'll be on the server at www.example.com. you can create the application locally on your development machine-perhaps a laptop you're using on an international flight-and later synchronize the work you 've ve done offline with the server. all your build files and any support files you 've added to the. net project are saved locally in c: \ Documents ents and Settings \ username \ vswebcache \ example.com \ mywebapp. it uses des hidden subdirectories such as _ vti_cnf and _ vti_pvt. according to the ASP. net documentation, files are pushed to vswebcache when you first work offline. then they're pushed to the server when you go back online or synchronize the files explicitly. it works fairly similarly to how it was supposed to work (but didn't) in Visual InterDev 6.0.

So vswebcache is usually a good thing, because it lets you store remote files locally so you can work on and run your site while you're offline. but you might never work on a remote site offline. I always build my sites on localhost, keep the files in visual sourcesafe on a machine accessible to both my development machine and the server, and then update the files to the server directly from sourcesafe. I never use offline mode, and until I researched this tip, I didn't even know where to turn it on in. net. (you select project | web project | Work Offline from the. net Main Menu .)