Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Jonathan Allen on Jul 18, 2007
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.
The 5 Mandates of Software Development Teams - Presto Manifesto
Agile Development: A Manager's Roadmap for Success
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
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 :)
I actually found nested master pages in VS2005 to be quite useful. They keep you (and your team) away from the designer :D
You are correct, I misspoke in that regard.
"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.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
4 comments
Watch Thread Reply