ASP'NET Best practices

1
ASP.NET Best practices ASP.NET 2.0 overview

• Alik Levin
• alikl_at_microsoft.com

2
Agenda

• ASP.NET best practices
• ASP.NET 2.0 overview

3
ASP.NET best practices

• Common look feel
• Code reuse
• DataSet and DataGrid
• Role based security
• Design patterns (Provider, MVC)
• Diagnostics

4
Common look feel

• A must for enterprise scale applications
• Can be implemented using
• User controls
• Base pages
• Both

5
Code reuse

• Custom controls
• To share across the projects
• Complex to implement
• Suitable for ISVs or infrastructure teams
• User controls
• To share inside project
• Easy to implement
• Visual designer support (partially)
• Use in design time or load dynamically

6
DataSet and DataGrid

• DataSet is great!
• I mean it is really big. I mean really heavy
• Use DataReader (read only, forward only)
• Implement custom collections using CollectionBase
  instead for biz objects
• DataGrid even greater
• Seen ViewState it generates?
• Use Repeater

7
Role based security

• Agnostic to underlying infrastructure
• Windows
• Forms
• Custom
• Trusted subsystem model
• Coding needed
• Application block available
• More business oriented than technical oriented

8
Design patterns - MVC

• Separation of duty
• Flexibility (for example, session management)

9
Design patterns - Provider

• Flexible for updates
• Agnostic to consuming app
• Configuration based behavior

10
Diagnostics

• Health monitoring
• Errors detection
• Business and security audit
• Use
• Built in trace, implement custom tracing
  mechanism
• Logging/Exception Management App Block
• EIF (WMI) for advanced users

11
Demo
12
ASP.NET 2.0 overveiw

• VS.NET 2005 project management
• Code enhancements
• Master pages
• Security enhancements
• Navigation enhancements
• User controls enhancements
• Skins and themes
• Compilation

13
VS.NET 2005 project management

• No more projects
• Point to directory and you are done
• No IIS/FPE needed
• Special folders
• I n t e l l i S e n c e everywhere
• even web.config

14
Code enhancements

• Partial classes
• Less auto generated code, cleaner
• Compiled in one single dll, no more temp dlls
• Generics
• Custom collections made easier

15
Master pages

• Common look and feel from template perspective
  no coding
• Visual designer support (at last)
• Object model support

16
Security enhancements

• Whole new family of controls
• You wrote a l-o-o-o-t of code before
• RBAC experience more than valuable
• Provider based
• Develop using Access
• deploy on SQL Server or AzMan
• Security Management Web site

17
Navigation enhancements

• Navigation controls
• SiteMapPath (breadcrumb)
• Menu
• Treview
• Provider based
• Wizard control

18
User controls enhancements

• Visual designer support
• WebParts

19
Skins and themes

• Common look and feel from graphical design
  perspective
• Kind of server side CSS
• Apply on
• Web site
• Page
• Control

20
Compilation

• V 1.1 compilation supported
• Pre compile prior deployment
• Better performance
• Can not update in prod (operations will love it)
• Strong Name signing made easier

21
Demo
22
Final thoughts (not mine)

• Any intelligent fool can make things bigger, more
  complex, and more violent. It takes a touch of
  genius -- and a lot of courage -- to move in the
  opposite direction."
• Albert Einstein
• Genius is one per cent inspiration and
  ninety-nine per cent perspiration. Accordingly, a
  'genius' is often merely a talented person who
  has done all of his or her homework
• Thomas Edison

23
Summary

• It all starts from design
• Many goodies out of the box in VS.NET2005
• Be genius and do your homework (see resources
  slide)

24
Resources

• http//www.microsoft.com/resources/practices/defau
  lt.mspx
• http//lab.msdn.microsoft.com/vs2005/
• http//msdn.microsoft.com/asp.net/
• www.asp.net
• http//msdn.microsoft.com/training/webcasts/
• http//xnetmentor.blogspot.com/
• http//www.idag.co.il/

25
(No Transcript)