There are, at least, six ways to have controls magically appear on a page at runtime. Just don't add it directly to the Page.
Microsoft has another solution for managing your Web.config file as you move your site to production. And, no matter what the name of this feature suggests, you don't have to learn XSLT to use it.
Peter Vogel raises some interesting questions that address one of the major benefits of ASP.NET MVC: Test Driven Development.
Peter Vogel wraps up his series on ASP.NET MVC, for now, by mapping some typical ASP.NET tasks to ASP.NET MVC.
Peter Vogel looks at the least important component of the ASP.NET MVC, the Model, and goes on to discuss a strategy for integrating the model, the controller and the view.
Peter continues his look ASP.NET MVC for ASP.NET developers (using the brand new version of ASP.NET MVC) by linking a view to a controller.
Peter Vogel begins his series on introducing ASP.NET developers to ASP.NET MVC by looking at the C in MVC: Controllers
Peter begins a series on educating traditional ASP.NET developers in the latest version of ASP.NET MVC. But first he looks at why he is not an ASP.NET MVC developer.
Sometimes, when the user clicks on a menu choice, you want to pass some data based on the page's content. Here's how to dynamically alter a menu control based on the data on the page.
If you'd rather keep your menu structure in a table in your database instead of a file in your Web site, here's all the code you need to implement a database-driven menuing system.
Creating your own module for managing menus is not only ridiculously easy, but opens the door for adding any other enhancements that you can think of.
ASP.NET 4 adds a wealth of features for client-side developers, including new ways of instantiating controls, a new infrastructure for managing libraries and some minor but much-needed tweaks. And there's more.
Peter considers two solutions for keeping items in the sitemap off of your Menu or TreeView controls. But he's also wondering if there are more solutions out there.
Peter Vogel closes out his eight-part series on creating an AJAX-enabled ASP.NET application.
Peter moves on from working with one record to working with multiple records and explores Microsoft's current templating solution.