Who is this Whidbey Guy? - A Personalization Framework in Whidbey
(Page 3 of 4 )
Taking this all to the next level, Microsoft is providing a 'complete' personalization framework, allowing us to easily and rapidly incorporate a customized user experience into our applications. Out of the box the system is able to store and persist such data as user information and preferences, using Access or SQL as data-stores, depending on the size of the site. And naturally we can extend the personalization framework to meet our specific needs.
Something else we can look forward to on a site-maintenance front, are what Microsoft has called 'Master Pages'. These work in conjunction with 'Content Pages' to form a fairly slick system of template management. This is a far deeper topic than this article could hope to cover, but you can look forward to digging far deeper in a short while.
It also seems that a lot of attention has been given to data access, and for good reason. Data controls in ASP.Net such as Repeaters and DataGrids simplified our lives immensely, becoming very popular. But while the DataGrid gave us incredible power with moderate flexibility and minimal code, there were noted efficiencies that could be put in place. Anything from simply removing those two redundant feeling lines (DataSource & DataBind) of code, to providing an entirely new control, called the GridView control. This is more or less a supercharged DataGrid, overhauling a few features of the DataGrid, and then going one giant leap further by providing component-based data filtering and selected line highlighting, again no need for additional code!
I've also seen hints and allegations of built-in test servers and completely mobile enable ASP.Net controls. You've really got to give credit to the ambitious minds behind the ASP.Net team! But really, the changes I've mentioned so far primarily deal with you and I, the developers. What can administrators look forward to?
Next: The Power of Whidbey >>
More ASP.NET Articles
More By Justin Cook
