views:

302

answers:

1

When I publish any type of asp.net application, my code is precompiled into various assemblies. I would like to avoid this so that I can upload an aspx page and its corresponding codebehind file. I understand the benefits of doing it either way, but what is desired here is the least risky way to publish changes.

How does one properly deploy an asp.net project without compiling assemblies?

Is the process different for each model (web app, MVC..)

+1  A: 

Sounds like you have a Web Application Project, and what you want is a Website Project. With website projects, you can modify the aspx and codebehind files and not have to worry about recompliling them, asp.net will do that for you. Web Application Projects need to be compiled for every code change.

Ely
If this functionality is desired, are we limited to only create website projects and forced to avoid MVC and Web Application?
splatto
I do believe that MVC is web application only. Might be wrong, but I've only seen MVC done in a web app model.
Ely
thanks for your answer
splatto