InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

VS 2008 to Support Nested Master Pages

Posted by Jonathan Allen on Jul 18, 2007

Sections
Development
Topics
Artifacts & Tools ,
.NET
Tags
ASP.NET ,
Visual Studio ,
Orcas

One of the most lauded features in ASP.NET 2.0 is Master Pages. Master Pages serve as templates for a site, making it easier to create and maintain consistent style site-wide. They do have one drawback under VS 2005: they cannot be nested.

Nested master pages are essential for larger sites that have more than one layout. Without them, developers have to manually ensure the common elements in each master page such as banners and copyright notices are kept in sync.

It turns out that nested master pages are actually supported by ASP.NET 2.0 itself. It is only in the Visual Studio 2005 IDE where they cannot be used. Visual Studio 2008 adds full support for nested master pages, allowing developers to switch to this model without losing IDE support.

It should be noted that since this feature is in ASP.NET 2.0, developers will not need to deploy .NET 3.5 to their production servers. They merely need to ensure that the project is set to compile to .NET 2.0.

Scott Guthrie has a walk-through of nested master pages on his blog. 


Visual visual studio? by Thom Nichols Posted
Re: Visual visual studio? by Eugen Anghel Posted
Re: Visual visual studio? by Jonathan Allen Posted
Re: Visual visual studio? by John DeHope Posted
  1. Back to top

    Visual visual studio?

    by Thom Nichols

    When you say "can't be used in the Visual Studio 2005 IDE," you mean they don't work in the visual designer, right? So I can still develop nested master pages from VS2005... Right?

    No matter - the visual designer is pretty crappy anyhow, I never used it :)

  2. Back to top

    Re: Visual visual studio?

    by Eugen Anghel

    I actually found nested master pages in VS2005 to be quite useful. They keep you (and your team) away from the designer :D

  3. Back to top

    Re: Visual visual studio?

    by Jonathan Allen

    You are correct, I misspoke in that regard.

  4. Back to top

    Re: Visual visual studio?

    by John DeHope

    "No matter - the visual designer is pretty crappy anyhow, I never used it :)"
    I agree if we're talking about VS 2003. But the VS 2005 designer is awesome, I must say. It's very robust, and the tag breadcrumbs are great. I just wish VS 2005 would target .Net 1.1 without fiddling so I could use it with my legacy 1.1 project.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.