Probably depends a lot on what's being included. ASP.NET doesn't "include" other code in this manner.
If the code being included is just PHP code, then there's no need for this in ASP.NET. The compiled assembly has all of the available code from the compilation already available.
If the code being included is actual page output, then it's a different model for how you'd accomplish this. The closest analogy would be to conditionally display a user control. Something like this:
if (status == 0)
{
var myControl = (MyControlType)LoadControl("~/MyControl.ascx");
myPlaceHolder.Controls.Add(myControl);
}
else if (status == 1)
{
var myOtherControl = (MyOtherControlType)LoadControl("~/MyOtherControl.ascx");
myPlaceHolder.Controls.Add(myOtherControl);
}
In this case, myPlaceHolder is an existing control on the page which exists solely as a, well, placeholder in order to add controls dynamically. This is because the page life cycle is different in ASP.NET than in PHP. In PHP the scripts are added in-line, whereas in ASP.NET the user controls are inserted into existing markup structure.