Using the ASP.NET 2.0 MultiView Control

Tabs controls have become a very common user interface feature in both Windows and Web applications, and its not surprising. They provide a way to reuse screen real-estate in an easy-to-understand and easy-to-navigate way.

However, ASP.NET 2.0 doesn't provide a tab control. Instead, it provides something even better: the MultiView. A MultiView is essentially a non-visual control that provides a pallette where you can drop several View controls. A View control is another non-visual control where you can place your user interface controls. Think of a MultiView as the tab control and the Views as tabs within it. The difference is that there's no built-in way to switch from one View to another. You can create your own "tabs" using command buttons or use whatever user interface element fits your design.

In this video, Bill Hatfield demonstrates how to add a MultiView to a page and switch among its Views using command buttons to simulate tabs.

About the Author

Bill Hatfield

Bill Hatfield is the best-selling author of numerous books for developers, including ASP.NET For Dummies, Active Server Pages For Dummies (on Classic ASP) and Visual InterDev For Dummies. He is also the editor of Visual Studio .NET Developer, a monthly technical journal from Pinnacle. He's an experienced corporate trainer and works in Indianapolis, IN where he also co-founded the local .NET group, the Indianapolis .NET Developers Association.


  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Enterprises are increasingly looking to platform as a service (PaaS) to lower their costs and speed their time to market for new applications. Developing, deploying, and managing applications in the cloud eliminates the time and expense of managing a physical infrastructure to support them. PaaS offerings must deliver additional long-term benefits, such as a lower total cost of ownership (TCO), rapid scalability, and ease of integration, all while providing robust security and availability. This report …

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date