Caching of compiled code. IIS or Web.Config-issue?

Peter S

Vote:

We've launched our site onto the public server and as the list of bugs grows I've stumbled on to a problem. When I upload code behind-files on the server the code never seems to be recompiled and I don't know if the problem lies in the IIS or in web.config. I've tried restarting the server, the site and the application pool but nothing helps. Only changes to web.config remains. Any ideas on how to fix this?

#37320

Mar 03, 2010 8:13

Frederik Vig

Vote:

You need to compile code-behind files and other class files into a binary file (assembly file), then drop it inside your sites bin folder (or make it strongly type and drop it in the GAC). *.cs files should not be on the server, only the .dll files.

This is because EPiServer uses the Web Application Project model, and not the Web site project model, where you can just drop the files inside your web sites folder, and they'll get compiled on the fly.

Hope this helps.

Frederik

#37321

Mar 03, 2010 8:44

Peter S

Vote:

That explains it. So if I compile in Visual Studio can I just replace the files in the bin-folder with the ones on the server?

#37323

Mar 03, 2010 8:46

Peter S

Vote:

Or if to put it this way: I've never worked with web application projects so what is the easiest way to go about if I want to make a small change to the site? In this example only to a couple of the files.

#37325

Mar 03, 2010 8:58

Peter S

Vote:

I just saw that you had already answered it. I missed that line...

Thanks! I'll give it a try!

#37326

Mar 03, 2010 9:00

Try our conversational search powered by Generative AI!

Caching of compiled code. IIS or Web.Config-issue?