Because ASP.NET applications are compiled and run before they are sent to the client, you cannot use a variable in place of a file name in a server-side include file (such as <!-- #include PathType = FileName -->"). However, you can use the Response or StreamReader object to write the include file to the HTTP content stream.
This article demonstrates how to create an .aspx page that reads a file with static HTML and/or client-side script code and writes the file's content to the browser.
back to the top
If you only want to write the content of a file to the browser, you can accomplish this in just one statement. If you want to manipulate the file before you send it to the browser, refer to the
References section for information about basic file input/output in .NET.
In ASP.NET, you can either write inline code or write code in the code-behind module. This article presents an inline code sample that opens a file and writes the file's content to the browser.
back to the top
- Open Microsoft Visual Studio .NET.
- From the File menu, point to New, and then click Project.
- In the New Project dialog box, click Visual Basic Projects under Project Types. Under Templates, click ASP.NET Web Application.
- Switch to the HTML code editor for the .aspx page that is created by default. Replace the existing code with the following code:
<%@ Page Language="vb" AutoEventWireup="false"%>
- Replace "Yourfile.inc" in the Response.WriteFile statement with the name of an include file that contains some HTML or client-side script.
- Add "Yourfile.inc" to the project.
- Browse to the .aspx file. Note that the content of your file is written to the browser.
- Server-side code in the dynamically included file is displayed on the client browser.
- If you use Response.Write or Response.WriteFile statements in a code-behind module, these statements write the information before any HTML tags. The same behavior occurs if you use inline <SCRIPT> tags with the RUNAT="Server" attribute.
Because the code-behind modules are compiled first, all of the output that is generated by Response.Write, Response.WriteFile, or inline server-side <SCRIPT> tags appears before any HTML tags when the HTML output is sent to the browser. This problem does not occur when you use Response.Write statements in classic ASP-style tags.