<< Pimp Your Firefox Install
|
Home
|
How SQL Server 2005's ROW_Number() Function Saved My Life >>
posted @ Tuesday, July 18, 2006 4:44 PM
Today while looking at something with a co-worker, we discovered a very useful VS2K5 feature. Have you ever (if you haven't, you aren't trying hard enough!) had problems with your site getting corrupted in your c:\windows\microsoft.net\framework\<VERSION>\Temporary ASP.NET Files directory? It results in strange, unuseful JIT Compilation errors, and rebuilding your app doesn't help. If you try to delete the files in the temp folder, you can't because they are locked by the VS process (for reasons I don't really understand).
The only way to fix it, that I had found until now, was to close VS, kill the aspnet_wp process, and delete the files, then re-open and rebuild. While that still turns out to be the cleanest way to do it, sometimes closing VS is not convenient, or not even an option. Enter the "Clean Solution" command found in the "Build" menu. This cleans out compiled files, frees up *most* of the locked files in "Temporary ASP.NET Files" and you can then "Rebuild Solution" and get the application up and running again. The downside is that it seems that it can happen again shortly thereafter as you continue to make changes, requiring you to repeat the process. So as mentioned, the one sure fire way to get it to stop is to close VS - but this can buy you time until you come to a convenient stopping point.
Technorati Tags:
asp.net. visualstudio