Building Effective Web
Applications with ASP .Net 3.5
• Prior web development experience
• Best geared towards programmers,
software engineers, web designers,
technical leads, task leads and architects.
• Class will be taught using C# which has a
similar syntax to Java
• Become familiar with new features in
ASP .Net 3.5
• Build database driven apps using
• Leverage ASP .Net AJAX on both the
client and server side
• Learn about state management and
• Secure your ASP .Net websites
• Week 1 – Getting Started
• Week 2 – Data Access, ADO .Net and
• Week 3 – AJAX
• Week 4 – State Management and Caching
• Week 5 – Security
• Week 6 – End to End app and SP1
Course Text and Code Samples
ASP .Net 3.5 Unleashed ( author
Stephen Walther - Sam’s
Code samples available for download at
o CD that accompanies the book has both
C# and VB .Net versions of the code
o Chapter 1 is available as a free
download from www.bookpool.com
o Demo how to run book code
Today’s Agenda – Getting
• Tools We Will Use
• ASP .Net 3.5 Overview
• Project Setup/Configuration
• WebForms Overview
• Server Controls
• User Controls
• Master Pages
• Debugging and Tracing
• New Features in ASP .Net 3.5
ASP .Net 3.5 Overview
• ASP .Net 3.5 is a technology that allows
programmers to create dynamic web
• ASP .Net can be used to create small
personal web sites or Enterprise
• ASP .Net is part of the .Net Framework
• .Net Framework consists of the
Framework Class Library and the
Common Language Runtime
Tools We Will Use
• VS 2008 Professional or
Visual Web Developer 2008
• SQL Server Express Edition or higher
(2005 or 2008)
Express Edition or higher
• Links to download these products can
be found on http://msdn.microsoft.com
• VS2008 available from MS, MSDN or
Team System subscription or contact Bill
Scherer Jr (SRA Enterprise Solutions
Working with .Net Projects –
• VS2003: Single solution file. Project precompiled into a single
DLL, ASPX markup pages deployed.
– Compiles/debugs like other projects (WinForms, etc.)
– Slightly more efficient.
– Single file deployment + referenced DLLs + HTML.
– Not easy to use in team environments.
– Often leads to monolithic DLLs for large sites.
Working with Projects - VS2005
VS2005: Website Compilation Model – All files
compiled on demand.
Works better in teams.
Easy to deploy/test incremental updates.
Can be difficult to upgrade from VS2003.
First hit incurs compilation overhead.
May mean more files to deploy.
Working with Projects - VS2008
• VS2008: Both models supported out
of the box. File -> New -> Web Site
File -> New -> Web Site
File -> New -> Project
-> ASP.NET Web App
Old style New style
• Create a new website using ASP .Net 3.5
Web Forms Key Points
• ASPX pages handled by a handler that
facilitate the page lifecycle and events (such
as Page_Load, PreRender, and control
• Uses ViewState to encoded state-specific
information otherwise lost in the stateless
nature of HTTP.
• Extensive controls library to abstract
functionality. Buttons, textboxes, etc.
• Web Forms have a .aspx file extension.
• Typically compiled into a DLL.
• Represents a small piece of
functionality, like a textbox or button.
• Responsible for handling any special
rendering requirements, raising
Properties Event Handlers
• Collections of HTML and/or Server
Controls for a broader purpose – such as
a login dialog box.
• Typically part of a project and compiled
with the project.
• Can expose properties.
• Take any HTML tag and add a
• This converts the HTML tag into a server-
side ASP .Net control
• Allow us to program server side events
• Same look and feel to many pages; code
in one spot.
• The HTTP Protocol is a stateless
• Web Pages use a
• ViewState allows us to save the state
of a server control across multiple
• Comes with performance overhead
• Enabled by default for each control
• Add page level tracing to existing
• Examine page lifecycle
• Examine Viewstate cost
• Write to trace log
• We can determine if the page is
posting back by using the
• We can turn tracing and debugging
Dynamic Compilation (p35)
• When we create an ASP .Net page
we are creating source code for a
• Pages are compiled and stored in a
temp folder on the web server
• Unlike classic ASP the page will not
be recompiled again, unless we
disable dynamic compilation
• This allows support for thousands of
Code Behind vs Single File
• In a single file ASP .Net page, a single file
contains both the page code and page
• A code behind has the page code in a
• Which should you use? (p45)
New Features of VS2008
• Nested Master Pages
• Enhanced CSS Management
• Multi-targeting support.
• New data controls.
• MUCH improved designer.
Other ASP .Net Resources
• MSDN Web site
• MSDN Virtual Labs
• MS Tech-ED Developer
presentations on my SRA portal site
• VS 2008 Training Kit
• Feel free to contact me at
• Thank you!