ASP.NET developers have always had two options for building controls for applications: user controls and server controls. Although server controls have their benefits, developers tend to gravitate toward user controls because of the designer support for building out the UI. SharePoint Web part developers are restricted to the server control realm which offers no UI designer support and often requires a great deal of code to define the UI directly in the control itself. Even simple UI changes require sifting through Web part code to determine where to make the change, and then the Web part needs to be recompiled and redeployed before the change takes effect. This session illustrates the use of templated Web parts, an architectural technique that separates Web part logic into the server control and the UI into one or more user controls. Developers are then free to use the designer tools in Microsoft Visual Studio and Microsoft Office SharePoint Designer to build out the UI for Web parts, and can make UI changes without the need to recompile or redeploy their Web parts. Templated Web parts also allows for other user experience possibilities like displaying alternate Uis based on user input, profile settings, security, or Web part configuration properties, and promotes code reuse because project-specific UI elements are maintained separately from the core Web part logic. As an added bonus, the it also contains built-in support for AJAX.NET components.