.net – safely delete the Temporary ASP.Net folder’s contents

asp.netiis-7net

My application works fine whenever I run under VS 2010. When I upload it on a server and I run from IIS it gives Complie error : CS0433:
'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\~\App_Web_dzybh5am.DLL' and 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\~\App_Web_znctdhjf.DLL'

Error:

Line 146:    
Line 147:    [System.Runtime.CompilerServices.CompilerGlobalScopeAttribute()]
Line 148:    public class default_aspx : global::_Default, System.Web.SessionState.IRequiresSessionState, System.Web.IHttpHandler {
Line 149:        
Line 150:        private static bool @__initialized;

A quick search on google revealed that deleting those temporary files solved the problem.

Is it useful to delete those temporary files, will it affect my application in future ?

I just want to know should I delete all files from temporary folder.

Best Answer

As long as your web app is shut down, it shouldn't have any effect on the application.
.Net / IIS uses that temp folder as a place to hold the compiled versions of your aspx/razor pages.

Keep in mind though that other IIS web apps may be using that temp folder, so be careful about when you do it.

Related Solutions

C# – Where does error CS0433 “Type ‘X’ already exists in both A.dll and B.dll ” come from

Theory

When this issue is not caused by a bug in the application (e.g., duplicate class name):

This issue appears to present after a change is made to the application's project that results in a new build (e.g., code/reference/resource change). The issue appears to lie within the output of this new build: for various reasons Visual Studio is not replacing the entire contents of your application's obj/bin folders. This results in at least some of the contents of your application's bin folder being out of date.

When said issue occurs, clearing out the "Temporary ASP.NET Files" folder, alone, does not solve the problem. It cannot solve the problem, because the stale contents of your application's bin folder are copied back into the "Temporary ASP.NET Files" folder the next time your application is accessed, causing the issue to persist. The key is to remove all existing files and force Visual Studio to rebuild every object, so the next time your application is accessed the new bin files will be copied into the "Temporary ASP.NET Files" folder.

Solution

Close Visual Studio
Perform an iisreset
Delete all the folders and files within the "Temporary ASP.NET Files" folder (the path is referenced in the error message)
Delete the offending application's "obj" and "bin" folders
Restart Visual Studio and open the solution
Perform a "Clean Solution" followed by a "Rebuild Solution"

Explanation

Steps 1-2: remove resource locks from the folders/files we need to delete.
Steps 3-4: remove all of the old build files
Steps 5-6: create new versions of the build files

C# – Get ASP.NET temporary folder path

Hmm. I didn't know that it would be so complicated. For the lack of better answer, I was able to come up with something like this:

using System.Runtime.InteropServices;

string net_base = Path.GetFullPath(Path.Combine(RuntimeEnvironment.GetRuntimeDirectory(), @"..\.."));
string strTemp32 = string.Concat(net_base, @"\Framework\", RuntimeEnvironment.GetSystemVersion(), @"\Temporary ASP.NET Files");
string strTemp64 = string.Concat(net_base, @"\Framework64\", RuntimeEnvironment.GetSystemVersion(), @"\Temporary ASP.NET Files");

There're obviously two temp folders -- for 32-bit and 64-bit processes. It is based on this sample, and also relies on the assumption that default ASP.NET temporary folders are hard-coded.

Correct me, if you find a better way?

Best Answer

Related Solutions

C# – Where does error CS0433 “Type ‘X’ already exists in both A.dll and B.dll ” come from

C# – Get ASP.NET temporary folder path

Related Topic