What are the differences between non-compiled and compiled ASP.NET pages

Got a situation where we have a working production website that is moving to a different group of servers. The team handling that site has gotten it to work without any issue (we can test it all day long.) The problem they are encountering is that in order for it to go live it has to compile/build without any errors.

It's an ASP.NET s开发者_高级运维ite built on the 2.0 framework. Not super complicated and to my knowledge it has never had to be compiled before now. Any changes done on the current production site involve just copying over .html and .aspx files.

What are the ramifications of not compiling the site before it goes live and deploying it as is? The team handling the deployment is saying that it's a security issue.

IIS will compile .as?x files as they are requested. You can have a bug in one and not find it till the page is loaded. If you create a web project (instead of a web directory), when you go to publish, a dll is compiled of ALL your code in the site. None of the .vb files are necessary at that point and only the compiled dll is requred in your /bin folder. This guarantees you DON'T have syntax errors in your code and you won't experience compile errors.