Website project is not and will never be outdated. Its to different models that both have their advantages and disadvantages.
Frankly speaking, its mostly a matter of how MSBuild behaves. We in Acto loves that its a normal Website project since it saves a lot of time not having to compile the whole website all the time. We then have some custom made msbuild configurations that runs on our Team City that performs the .config transformation, does the same pre-compilation as the "WebApplication" does in Visual Studio and also removes some codebehind .cs files.
IMHO its a mess that you in a WebApplication can have codefiles spread out in other folders than App_Code. I understand that its convenient for MVC applications where you just want to have your controllers and models next to css and js files but I would always prefer to have "heavy" code in a separate Class Library project though, which you can Unit Test as much as you want, use Edit and Continue and more.
Saying that its a security issue to have code on disk on your website seems like a big leap, IIS doesn't allow downloading of .cs, .vb or any other code files. Doing a naive pre-compilation has other implications like removing .master and .ascx files completely which in turn breaks functionality of the Master Page templates and UserControl functions in C1 since it relies on these files being present on the disk.
Frankly speaking, its mostly a matter of how MSBuild behaves. We in Acto loves that its a normal Website project since it saves a lot of time not having to compile the whole website all the time. We then have some custom made msbuild configurations that runs on our Team City that performs the .config transformation, does the same pre-compilation as the "WebApplication" does in Visual Studio and also removes some codebehind .cs files.
IMHO its a mess that you in a WebApplication can have codefiles spread out in other folders than App_Code. I understand that its convenient for MVC applications where you just want to have your controllers and models next to css and js files but I would always prefer to have "heavy" code in a separate Class Library project though, which you can Unit Test as much as you want, use Edit and Continue and more.
Saying that its a security issue to have code on disk on your website seems like a big leap, IIS doesn't allow downloading of .cs, .vb or any other code files. Doing a naive pre-compilation has other implications like removing .master and .ascx files completely which in turn breaks functionality of the Master Page templates and UserControl functions in C1 since it relies on these files being present on the disk.