Clean conflicting class files from Temporary ASP.NET Files

Question

Class file Conflicts in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\ is preventing me from building the solution. Even though I try emptying out the folder, each time Visual Studio starts the build process, it brings in the class file in to the temp folder with the same folder name. If I restart the machine or leave it overnight, project build without error. Is there anyway to tell Visual studio to delete/ignore/clean any lingering class files that could be in the temp folder?

Clean solution option in VS doesn't work either. Class file in conflict are from the App_Code folder.

related http://stackoverflow.com/questions/3932677/what-is-the-shortcut-to-clear-temporary-asp-net-files-folder-before-runing-appl — Maslow, Sep 27 '11 at 20:23
also related with some very good info http://stackoverflow.com/questions/586790/eliminating-temporary-asp-net-files/592673#592673 — Maslow, Sep 27 '11 at 20:24

score 10 · Accepted Answer · edited May 23 '17 at 11:46

10

Adding this as an answer here directly: move the temp location for easier cleaning or a pre-build event

<system.web>

   <compilation tempDirectory="d:\TempASP.NETFiles\">

      ...

   </compilation>

</system.web>

Source was the SO answer, which lead to this: http://blog.cwa.me.uk/2007/10/15/relocating-temporary-aspnet-files/

edited May 23 '17 at 11:46

Community

1
1

answered Sep 27 '11 at 20:26

Maslow

18,464
20
106
193

score 5 · Answer 2 · answered Apr 22 '10 at 00:18

5

Clean, Close all instance of VS, delete the temp files, empty recycle bin, throw pinch of salt over left shoulder. start VS and rebuild all.

works for me at the odd times this happens

answered Apr 22 '10 at 00:18

Sky Sanders

36,396
8
69
90

1

We just threw a pinch of salt over our shoulder in production! – Dave Haynes Dec 19 '12 at 20:24
2

The salt is the key step – pstricker Jan 22 '16 at 18:32

score 0 · Answer 3 · answered Apr 21 '10 at 21:27

0

Check that you have not compiled DLL file and not compiled equal class in a project.

answered Apr 21 '10 at 21:27

Anton

9,682
11
38
68

score 0 · Answer 4 · answered Apr 21 '10 at 21:46

0

Use a pre-build operation on the project to make sure the folder is cleared, it's possibly IIS auto-compiling your app before serving it.

answered Apr 21 '10 at 21:46

Aren

54,668
9
68
101

How do you setup pre-build operations to clean these folders? Thanks – Deepfreezed Apr 22 '10 at 13:41

score 0 · Answer 5 · answered Apr 21 '10 at 22:01

0

I think it's that you have two class names that are the same: One in your APP_Code and another class as the name of a user control or page.

answered Apr 21 '10 at 22:01

Saturn K

2,705
4
26
38

This was correct the first time I tried to compile. But then I deleted the conflicting class but the problem did not go away. – Deepfreezed Apr 22 '10 at 13:36

score 0 · Answer 6 · answered Mar 27 '18 at 10:48

I have faced the similar kind of issue in my project. The files were facing infliction between the files having same name from the current project and an another project. I have resolved it by deleting the files from my project's bin directory whichever i don't wanted.(Still if the problem is not resolved, delete the unwanted files & temporary files from "Debug" and "Release" folders.). This worked 100% in my case.

score 0 · Answer 7 · answered Feb 17 '23 at 01:29

My problem was that this error was popping up when deploying in Azure using pipelines. Looked into the "Temporary ASP.NET folder" to clean it up, but it was empty. To fix the issue I packed the class into a namespace and updated the references to use the full Namespace.Class type.

Clean conflicting class files from Temporary ASP.NET Files

7 Answers7

Linked