Geeks With Blogs

News

  
Bill Evjen's Blog Code, Life and Community

ASP.NET Whidbey Themes

 

Developer productivity

  • Reduce ASP.NET V1-V2 lines of code by 2/3rds
  • Enable rich scenarios not easily possible today

Administration and Management

  • Easiest platform to manage and administer

Totally Extensible Platform

  • Replace/extend all built-in features + services
  • Customize for any enterprise environment

 

Performance and scalability

  • The world’s fastest web application server

 

Runs on a 64-bit server

 

ASP.NET 2.0 Developer Stack

  • New ASP.NET Building block APIs
    • Membership.
    • Role Manager
    • Personalization
    • Site Navigation
    • Database Caching
    • Management

 

Rich MMC admin tool

Every section of the web.config file is represented here.

 

Instrumenting code – something happens in your code – can send out a notification – email is an example. “Only send me a notification once an hour”.

 

Provider model Design Pattern – under all the APIs

Abstract all the storage mechanisms into provider classes. You can implement if you want to use your own underlying data stores.

These building blocks can then use your custom data stores via these providers.

Oracle or LDAP are examples.

This will work with existing APIs as well.

 

On top of building block APIs are new ASP.NET Whidbey “Page Framework” Features

  • Master Pages
  • Themes/Skins
  • Adaptive UI – to mobile devices – mentioned that this is around the Whidbey time frame. In the Longhorn timeframe – adapt to the Longhorn client – XAML output for Avalon.

 

40+ new controls

  • Security
  • Data
  • Navigation
  • Web Parts

 

Some of these controls talk to the underlying APIs. Breadcrumb controls. Introducing Web Parts (shipped a week ago as part of Office 11). Taking the notion of Web Parts and baking it directly into ASP.NET. Any control that is built in ASP.NET can take advantage of this.

 

ASP.NET Application Hosting

  • ASP.NET App-Model extended to support non-HTTP
    • Key Scenario: Indigo Services
  • Unified Application Model for Web/Service Apps
    • Membership and Role Management
    • Missed the rest….

 

Indigo Hosting Port > Service.svc

 

This was all about ASP.NET the runtime. Now looking at ASP.NET the tool.

 

Web Development in Visual Studio

Major improvements for Whidbey

  • FrontPage Server Extensions No Longer Required
    • Now file system, IIS, FTP and FPSE Web Sites
  • Directory Based Project System Model
    • Edit any web anywhere (no project file required)
    • Dramatic performance improvements with large web sites
    • No longer required to build entire site into a single DLL
  • HTML Source Preservation
    • Tool will never re-format (BIG applause)
  • Intellisense Everywhere
    • Code behind, Inline code, HTML, CSS, ASP.NET page directives, Web.config, XML files, etc.
  • HTML Tag Navigator and Tag Outlining
    • Easily view, navigate + explore complex pages
  • XHTML Support w/ pluggable validation engine
  • Rich Master page Design – time support
  • Enhanced ASP.NET Code-behind page editing
    • Cleaner and more oo code editing support
    • Removes brittleness of current tool wire-up
  • ASP.NET single File page editing support
  • Built in ASP.NET Web service (no IIS required)
    • Only allows local browser requests
    • Automatic shutdown when VS IDE is closed
    • Meant for development
  • Publish Web
    • Easily synchronize/publish webs between servers
  • Rich data design time support
  • Much much more….

 

In his demo, Scott created a new project and there were no project files. Created a pageable, sortable datagrid with no code needed. The Query Editor in VS.NET takes care of working with parameters in the wizard – quite easy! The control that he was using is the <asp:gridview> control. Also can bind against web services or a middle-tier object layer instead.

 

Sqlcachevalidation is quite impressive. So this means that instead of a table changing based upon time limits, it will actually change when the database changes.

 

Master pages have a @ master directive instead of an @ page directive.

 

?>

Posted on Monday, October 27, 2003 3:23 PM | Back to top


Comments on this post: Scott Guthrie's Talk - WSV200 - Overview of ASP.NET Whidbey

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Bill Evjen | Powered by: GeeksWithBlogs.net