ASP.NET Web项目（C＃）是否有按需编译选项？

Question

I just started working with an ASP.NET application that has been converted from a VB.NET web site to a C# web project and I am finding that my development time is significantly longer using C# than VB.NET.

When I am editing a simple line of code in an C# code behind file, I have to manually recompile the entire site just to see the result of the change. In with the web site, I could edit a code behind file and then execute it in the browser to see the result of the change without doing a compile (or alternatively, right-click and choose compile page).

My question is, is there an option somewhere to compile JUST THE ONE PAGE? If not, is there something that can be done (other than getting more hardware or converting the project back to web site) to speed up the development/debugging process?

Clarification

In a ASP.NET (VB) Web Site project I can make an edit in code-behind, click the save button, then open up a browser and navigate to the page to instantly see the change (or at least within 5 seconds). In a Web Application Project in ASP.NET (C#), I am finding I have to compile the entire web site to view the live change in a browser (a process that takes upwards of 2 minutes).

Answer 1

You can build your solution at any time by pressing Ctrl + Shift + B .

Right-click and Exclude any projects/folders/files you don't want to include.

EDIT : A Web Application Project has to be built in its entirety, but Visual Studio only builds those files which have changed so this shouldn't be too slow for you.

In a Web Site Project, Visual Studio completely compiles Web site projects whenever you run or debug any page by default - but - you can change the build project option to compile only the current page on run or debug.

Answer 2

Your .aspx and .ascx should reference their codehind files through CodeFile instead of CodeBehind. Then the codebehin will be compiled on demand.

<%@ Page Language="C#" AutoEventWireup="true" EnableViewState="true" CodeFile="myPage.aspx.cs" Inherits="myPage" %>

instead of

<%@ Page Language="C#" AutoEventWireup="true" EnableViewState="true" CodeBehind="myPage.aspx.cs" Inherits="myPage" %>

There are some drawbacks though :

• CodeBehind pages can not use CodeFile controls (but codefile pages can use any kind of controls)
• referencing codefile controls is a bit more complicated
• you will lose sync with the .designer.cs and have to reswitch to codebehind for a second to resync.

On the long run, CodeFile will save you a lot of time.