In an ASP.NET website with a codebehind at what point are the .cs files compiled?

In Brief:
In an ASP.net website with a code-behind, at what point are the *.cs files compiled?

Context:
A colleague who has since left, deployed a website with a .cs code-behind to a shared server. I have made a small change to a .cs file, which I should expect to reflect on one of the pages but it has not yet appeared. I have restarted the application pool, however I am loathe to reset IIS on the server as there are couple of other teams’ apps which might be be in use on the same server.

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

This applies to Web Application projects as opposed to Web Site projects, which are CodeFile by default, and don’t allow changing the build action…

In ASP.NET Web Applications you have two methods of deploying your pages; CodeFile and CodeBehind. By default pages will always use CodeBehind but you can change this.

CodeBehind

CodeBehind compiles your .cs file into the .dll file in your bin folder at compile/build time, and then you deploy that to your web server. There is no need to deploy the .cs file to your web server. If you do, it will just sit there being unused.

To configure a page with CodeBehind, ensure that:

• The page directive in your .aspx file has CodeBehind="your.aspx.cs"
• The properties of the .cs and .designer.cs files in solution explorer have a build-action of compile.

CodeFile

This causes ASP.NET to compile the .cs file on-the-fly on the server. This means that your .cs file needs to be deployed to the web server. It also means that your .cs file will not be compiled at compile/build time and therefore not built into your .dll in the bin folder.

Key advantage

With CodeFile, You can make changes to the .cs file and deploy just that file to see the changes on your production web server. No need to re-deploy. No need to recycle the app pool. This can be very useful in a lot of situations.

To configure a page with CodeFile, ensure that all of the following are met:

• The page directive in your .aspx file has CodeFile="your.aspx.cs"
• The properties of the .cs file in solution explorer have a build-action of content
• The properties of the .designer.cs file in solution explorer have a build-action of none.

Notes

• Intellisense doesn’t like working when pages are set up with
  CodeFile (you can change to CodeBehind whilst coding and then change back for deployment, though).
• If you change from CodeBehind to CodeFile, then always do a
  rebuild and re-deploy (and vice versa). This is because when the page was CodeBehind,
  the .cs was compiled into the .dll in the bin folder, and will
  remain there when you change to CodeFile. The CodeFile will be
  compiled on-the-fly and you will get the same code/classes defined in
  the .dll and in the on-the-fly compiled code, which will lead to
  runtime errors.

Method 2

For the setup I use, the .cs files are compiled when building the project. This means it is the .dlls in the bin that need to change, not the .cs files directly.

The .aspx files can change at any time, but I think you need to rebuild the project in order for the code behind to take effect.

I have replaced singular .dlls before without any problem (though it’s not good practice).

Method 3

Apparently what you have done should work.
Check if Cacheing has been implemented.
Otherwise publish the code and deploy the dll, instead of .cs file. I would recommend to test in staging server before you go live.

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0