A naive approach is to simply copy and paste the common layout markup into all web pages, but this approach has a number of downsides. For starters, every time a new page is created, you must remember to copy and paste the shared content into the page.
Such copying and pasting operations are ripe for error as you may accidentally copy only a subset of the shared markup into a new page. And to top it off, this approach makes replacing the existing site-wide appearance with a new one a real pain because every single page in the site must be edited in order to use the new look and feel. Prior to ASP. NET version 2. This approach required that the page developer remember to manually add the User Controls to every new page, but allowed for easier site-wide modifications because when updating the common markup only the User Controls needed to be modified.
Unfortunately, Visual Studio. NET 1. A master page is a special type of ASP. NET page that defines both the site-wide markup and the regions where associated content pages define their custom markup. As we will see in Step 1, these regions are defined by ContentPlaceHolder controls.
The ContentPlaceHolder control simply denotes a position in the master page's control hierarchy where custom content can be injected by a content page. The core concepts and functionality of master pages has not changed since ASP. However, Visual Studio offers design-time support for nested master pages, a feature that was lacking in Visual Studio We will look at using nested master pages in a future tutorial.
Figure 2 shows what the master page for www. Note that the master page defines the common site-wide layout - the markup at the top, bottom, and right of every page - as well as a ContentPlaceHolder in the middle-left, where the unique content for each individual web page is located.
Once a master page has been defined it can be bound to new ASP. NET pages through the tick of a checkbox. These ASP. NET pages - called content pages - include a Content control for each of the master page's ContentPlaceHolder controls.
When the content page is visited through a browser the ASP. NET engine creates the master page's control hierarchy and injects the content page's control hierarchy into the appropriate places. This combined control hierarchy is rendered and the resulting HTML is returned to the end user's browser. Consequently, the content page emits both the common markup defined in its master page outside of the ContentPlaceHolder controls and the page-specific markup defined within its own Content controls.
Figure 3 illustrates this concept. Now that we have discussed how master pages work, let's take a look at creating a master page and associated content pages using Visual Web Developer. In order to reach the widest possible audience, the ASP. NET 3. If you have not yet upgraded to ASP. NET 2. However, some demo applications may use features new to the.
NET Framework version 3. Do keep in mind that the demo applications available for download from each tutorial target the. NET pages' code-behind classes. Long story short, if you have yet to install. See Dissecting ASP. NET Version 3. You will also need to remove the using statements that reference 3. Before we can explore creating and using master and content pages, we first need an ASP.
NET website. Start by creating a new file system-based ASP. Choose the ASP. This will create a new web site with a Default. I use the Web Site Project model for my demos in this tutorial series. This site uses Akismet to reduce spam. Learn how your comment data is processed. Checking the Visual Studio installer If we scroll all the way to the bottom of the list of available templates, we can click on the " Install more tools and features " link, which will open the Visual Studio Installer.
Individual components for. NET Inside the. Hovering over the component, the tooltip describes it as: Enables. This component looked like exactly what could solve the problem, so I selected and installed it.
Note: Installing. NET Framework project and item templates component also adds another. Tweet Share Pin Reddit. Related Posts.
Read More. Rahul S November 14, Thanks a lot for your help God bless V November 18, Worked for me. Fritz November 19, Oscar November 21, Thanks, it worked! Sidhant November 26, Thank you so much! Francesco November 27, Thank you! Pouypm November 29, These content pages are based on the default master. For more information, see ASP. Use this project template to create web applications that use a model-view-controller pattern, using the ASP. The MVC pattern helps separate the different aspects of the application input logic, business logic, and UI logic , while providing a loose coupling between these elements.
In addition, this project template promotes test-driven development TDD. This template creates an ASP. NET web application that includes a Web. Use this project template when you do not require the functionality built into the standard template. NET Entity Framework. This type of Dynamic Data web application can target any relational database. Dynamic Data automatically generates a functional web application for viewing and editing data, based on the schema of the data.
Use this project template to create a web server control for ASP. The control consists of server and client code that work together to produce rich client behavior. Use this project template to create an Ajax component that enhances the client capabilities of standard ASP. NET web server controls. Use this project template to create a custom ASP. NET Web Forms pages. NET Server Controls.
All docs. The page you are viewing does not exist in version This link will take you to the root page. General Information. DevExpress Installation. DevExpress Code Examples. Common Tools Project Converter. Assembly Deployment Tool. Localization Service. Quality Assurance and Productivity. CodeRush Classic. TestCafe Studio. Controls WinForms. UWP Windows Tools WinForms Skin Editor.
0コメント