相当于服务器端的 ASP.NET 包括

本文介绍了相当于服务器端的 ASP.NET 包括的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

Although the classic ASP method of server-side includes works in ASP.NET, I get the impression it is not the preferred method. How am I "supposed" to be achieving the same effect?

This is how I'm doing it at the moment: <!-- #include file ="functionlib.aspx" -->

解决方案

You now have a number of options that provide this effect, but in a different manner.

• User Controls (.ascx)
• Master Pages (.master)
• Server Side Controls (.dll)
• Class Libraries (.dll)
• App_Code Classes (.cs/.vb)

Each are used for differently to achieve different things. It depends what you're really trying to do. Given the name of your include file, I'd imagine you're trying to include library functions that will be used within the context of your page.

Consequently you'd write a class library that contains the methods and import them into your application/aspx.

If you're looking at templating a page that will do most of the layout work to provide a body for differing content then you'll be interested in Master Pages.

If you're looking at templating controls that can be used in many pages, then you're going to be after User Controls.

If you're looking at templating controls that can be used by many users across many projects, then you'll be looking at Server Side Controls.

If you're looking at a library of classes/methods then you'll develop a class library or use an app_code class which can be JIT compiled the first time it's called. This could at a stretch be considered more like classic ASP, but really it functions more like a class from a class library as a single unit. You can call it from within your codebehind or within <% %> tags in your aspx/ascx code without requiring a reference to a class library.

We don't really use "includes" per se any more, but each of these tools in your toolkit allow you to provide similar concepts for different scenarios. As a developer you will interact with the entire page lifecycle of your web pages differently. ASP.NET is a very different beast than classic ASP. It truly takes a different view/approach and will take some amount of patience to figure out the differences.