1

I develop a simple file manager inside an ASP.NET Web site (not web application).

I notice that every time I rename or delete a folder, the site gets recompiled - i.e. the very next web request after delete or rename operation takes considerably much time to execute.

It's only true for folders, not for files. Why does this occur?

P.S. I use WebDev server (Cassini), haven't tested in on IIS yet.

UPDATE: The same disaster happens with ASP.NET MVC Web Applications :(

UPDATE 2: Here are similar discussions:

Community
  • 1
  • 1
amartynov
  • 4,125
  • 2
  • 31
  • 35

3 Answers3

1

Asp.net watches the folders and then runs compilation to keep up with any changes you make. To overcome this you can use Non-updateable full precompilation, which you can read about here.

Jason Webb
  • 7,938
  • 9
  • 40
  • 49
  • It is still recompiling on you or it doesn't allow you to create folders? Also I just noticed you are using the dev server. That is most likely part of the issue. Maybe try it out on IIS and see if it is still recompiling. – Jason Webb Apr 26 '10 at 20:54
  • BigJason: same on IIS, same on all types of web apps, you delete or rename forder and app gets recycled. – amartynov Apr 29 '10 at 07:56
1

You should move the files folder outside the project structure and probably use a virtual folder in IIS to keep the paths. This should not only prevent recompilation but will also make updating the code and backing up the user files easier because they will be separated.

Stilgar
  • 22,354
  • 14
  • 64
  • 101
0

Where are the folders you are creating? Under App_Data?

Raj Kaimal
  • 8,304
  • 27
  • 18