Migrating to Clint Edmonson Architect Evangelist Microsoft

Background Upgrading from Classic ASP Upgrading from .NET 1.1 Upgrading from VS 2003 Upgrading from Server 2003 General Recommendations Futures Resources

Background

Upgrading from Classic ASP

Upgrading from .NET 1.1

Upgrading from VS 2003

Upgrading from Server 2003

General Recommendations

Futures

Resources

Review of Classic ASP/COM+… Classic ASP = ASP, COM+, ADO Components & Interfaces registered as GUIDs and string names COM+ runtime acts as object factory Reference counting memory management system ASP pages compiled and cached by scripting engine as they are requested

Review of Classic ASP/COM+…

Classic ASP = ASP, COM+, ADO

Components & Interfaces registered as GUIDs and string names

COM+ runtime acts as object factory

Reference counting memory management system

ASP pages compiled and cached by scripting engine as they are requested

Review of ASP.NET technology… Assemblies (EXEs & DLLs) are loaded as they are used Preferential load locations (GAC, local folder, framework folder) Classes are JIT compiled from intermediate code as they are used Common Language Runtime (CLR) creates objects and manages memory using garbage collection algorithms Global Assembly Cache (GAC) ASP.NET pages are compiled at request time

Review of ASP.NET technology…

Assemblies (EXEs & DLLs) are loaded as they are used

Preferential load locations (GAC, local folder, framework folder)

Classes are JIT compiled from intermediate code as they are used

Common Language Runtime (CLR) creates objects and manages memory using garbage collection algorithms

Global Assembly Cache (GAC)

ASP.NET pages are compiled at request time

Review of Server + IIS technology… Server 2000 + IIS 5 Classic ASP files run in IIS process COM+ code must run out-of-process or in the IIS process All ASP.NET applications run in a single ASP.NET worker process (can be isolated if necessary) Server 2003 + IIS 6 Introduced concept of multiple worker processes (application pools) COM+ remains the same ASP files run within the same worker process as ASP.NET applications Virtual applications are assigned to a specific application pool Each pool is assigned to a specific version of the .NET framework

Review of Server + IIS technology…

Server 2000 + IIS 5

Classic ASP files run in IIS process

COM+ code must run out-of-process or in the IIS process

All ASP.NET applications run in a single ASP.NET worker process (can be isolated if necessary)

Server 2003 + IIS 6

Introduced concept of multiple worker processes (application pools)

COM+ remains the same

ASP files run within the same worker process as ASP.NET applications

Virtual applications are assigned to a specific application pool

Each pool is assigned to a specific version of the .NET framework

Classic ASP & ASP.NET can coexist Both types of pages can live in the same application Allows for gentler migration Application can be re-architected from inside out Separate files, processed by separate engines Warning: Session & Application state are not shared between engines

Classic ASP & ASP.NET can coexist

Both types of pages can live in the same application

Allows for gentler migration

Application can be re-architected from inside out

Separate files, processed by separate engines

Warning: Session & Application state are not shared between engines

.NET supports COM+, but… Two completely different memory management approaches Easy to expose .NET classes as COM+ objects and use them in classic ASP Warning: Much harder to use COM+ inside .NET

.NET supports COM+, but…

Two completely different memory management approaches

Easy to expose .NET classes as COM+ objects and use them in classic ASP

Warning: Much harder to use COM+ inside .NET

.NET 1.1 apps run under 2.0, 3.0, and 3.5 In fact, your web apps will be running on .NET 2.0 You will still need VS 2003 if you intend to keep them 1.1 Warning: Some minor incompatibilities and changes between 1.1 and 2.0 Dynamic Page Naming scheme changed – code using reflection to determine page name will break Dynamic naming scheme of controls in grids and lists changed System.Threading.Monitor class bug fixes – # calls to Monitor.Enter() must equal number of calls to Monitor.Exit() Keep-Alive default setting on Web Service proxies changed from false to true Others…

.NET 1.1 apps run under 2.0, 3.0, and 3.5

In fact, your web apps will be running on .NET 2.0

You will still need VS 2003 if you intend to keep them 1.1

Warning: Some minor incompatibilities and changes between 1.1 and 2.0

Dynamic Page Naming scheme changed – code using reflection to determine page name will break

Dynamic naming scheme of controls in grids and lists changed

System.Threading.Monitor class bug fixes – # calls to Monitor.Enter() must equal number of calls to Monitor.Exit()

Keep-Alive default setting on Web Service proxies changed from false to true

Others…

New in .NET 2.0 Master Pages Generics Anonymous classes Partial classes Caching library Built in Membership, Role, and Personalization framework Login control Web Parts & Zones Many, many performance optimizations

New in .NET 2.0

Master Pages

Generics

Anonymous classes

Partial classes

Caching library

Built in Membership, Role, and Personalization framework

Login control

Web Parts & Zones

Many, many performance optimizations

New in .NET 3.0 Built on top of 2.0 Windows Presentation Foundation (WPF) Windows Communication Foundation (WCF) Windows Workflow Foundation (WF) Identity Management Metasystem (CardSpace) Minor point release update to .NET 2.0 included

New in .NET 3.0

Built on top of 2.0

Windows Presentation Foundation (WPF)

Windows Communication Foundation (WCF)

Windows Workflow Foundation (WF)

Identity Management Metasystem (CardSpace)

Minor point release update to .NET 2.0 included

New in .NET 3.5 Built on top of 2.0 and 3.0 ASP.NET Ajax Membership, Role, and Personalization framework exposed as web services Language Integrated Querying (LINQ) Native support for latest web protocols (RSS, JSON, etc) Implicitly typed local variables Object and collection initializers Extension methods Auto-implemented properties

New in .NET 3.5

Built on top of 2.0 and 3.0

ASP.NET Ajax

Membership, Role, and Personalization framework exposed as web services

Language Integrated Querying (LINQ)

Native support for latest web protocols (RSS, JSON, etc)

Implicitly typed local variables

Object and collection initializers

Extension methods

Auto-implemented properties

New in VS 2005 Support .NET 2.0 framework projects only Two Project Styles: Web Sites and Web Applications Integrated micro-web server for debugging Class browser Interactive object test bench Code snippets Refactoring wizards Debugger data-tips

New in VS 2005

Support .NET 2.0 framework projects only

Two Project Styles: Web Sites and Web Applications

Integrated micro-web server for debugging

Class browser

Interactive object test bench

Code snippets

Refactoring wizards

Debugger data-tips

New in VS 2008 Completely replaces VS 2005 Multi-targets version 2.0 and higher runtimes Designers and toolboxes adapt to runtime selection JavaScript intellisense JavaScript debugging New CSS editor Unit test automation tools (in all SKUs)

New in VS 2008

Completely replaces VS 2005

Multi-targets version 2.0 and higher runtimes

Designers and toolboxes adapt to runtime selection

JavaScript intellisense

JavaScript debugging

New CSS editor

Unit test automation tools (in all SKUs)

New in Windows Server 2008 & IIS 7 Windows Activation Services Completely configurable request pipeline Support for URL rewriting

New in Windows Server 2008 & IIS 7

Windows Activation Services

Completely configurable request pipeline

Support for URL rewriting

Adoption Guidance Complete rewrite should be a last resort Upgrade based on strategic importance and maintenance overhead Partial conversion Convert as upgrades are needed Add only the new features in .NET Leverage application pools for migration Create separate 1.1 and 2.0 pools on your servers Test 1.1 apps under 2.0 runtime and move them over if successful Even 1.1 apps will see a 5-15% performance improvement Code conversion effort is low, remediation testing will be your big cost 99% of your apps will take less than 1 day to upgrade Finding that 1% is the expensive part

Adoption Guidance

Complete rewrite should be a last resort

Upgrade based on strategic importance and maintenance overhead

Partial conversion

Convert as upgrades are needed

Add only the new features in .NET

Leverage application pools for migration

Create separate 1.1 and 2.0 pools on your servers

Test 1.1 apps under 2.0 runtime and move them over if successful

Even 1.1 apps will see a 5-15% performance improvement

Code conversion effort is low, remediation testing will be your big cost

99% of your apps will take less than 1 day to upgrade

Finding that 1% is the expensive part

Architectural Guidance Keep your UIs dumb Separate UI logic from business and data access logic Leverage databinding Practice Service Oriented Thinking Share your business capabilities, not your databases Look for cross platform Enterprise Application Integration opportunities (.NET, JAVA, SAP, SIEBEL, …) Develop a set of shared enterprise components & services Security (Authorization, Authentication) Event Logging & Notification Database Location & Access Service Location & Access Encryption

Architectural Guidance

Keep your UIs dumb

Separate UI logic from business and data access logic

Leverage databinding

Practice Service Oriented Thinking

Share your business capabilities, not your databases

Look for cross platform Enterprise Application Integration opportunities (.NET, JAVA, SAP, SIEBEL, …)

Develop a set of shared enterprise components & services

Security (Authorization, Authentication)

Event Logging & Notification

Database Location & Access

Service Location & Access

Encryption

Other Tips… Use the Web Application project type in the enterprise Don’t try to code .aspx pages like .asp pages Put all server side code in code-behind files Avoid using Application & Session state if at all possible Application variables are not distributed in a web farm Session state in a farm is often slower than direct DB calls because of serialization overhead Watch out for XML and Regular Expressions XMLDocuments cause heavy CPU load – use XMLReader/Writers Regular expressions generate dynamic .NET assemblies

Other Tips…

Use the Web Application project type in the enterprise

Don’t try to code .aspx pages like .asp pages

Put all server side code in code-behind files

Avoid using Application & Session state if at all possible

Application variables are not distributed in a web farm

Session state in a farm is often slower than direct DB calls because of serialization overhead

Watch out for XML and Regular Expressions

XMLDocuments cause heavy CPU load – use XMLReader/Writers

Regular expressions generate dynamic .NET assemblies

.NET 4.0 and Beyond* Will strive to continue additive framework strategy Support for running multiple runtimes in the same process is being proven out right now Technology POCs are made available regularly on CodePlex ADO.NET Entity Framework and LINQ to Entities ADO.NET Data Services Model-View-Controller (MVC) Framework More to come… * These statements and features are subject to change and no guarantees are implied.

.NET 4.0 and Beyond*

Will strive to continue additive framework strategy

Support for running multiple runtimes in the same process is being proven out right now

Technology POCs are made available regularly on CodePlex

ADO.NET Entity Framework and LINQ to Entities

ADO.NET Data Services

Model-View-Controller (MVC) Framework

More to come…

Where to go next… Converting ASP to ASP.NET Debugging Classic ASP Code in VS 2005 Migrating from Classic ASP to ASP.NET (webcast) Upgrading to Microsoft .NET Visual Studio 2008 & .NET 3.5 Training Kit

Where to go next…

Converting ASP to ASP.NET

Debugging Classic ASP Code in VS 2005

Migrating from Classic ASP to ASP.NET (webcast)

Upgrading to Microsoft .NET

Visual Studio 2008 & .NET 3.5 Training Kit

Clint Edmonson Architect Evangelist Microsoft [email_address] http://www.notsotrivial.net

Clint Edmonson

Architect Evangelist

Microsoft

[email_address]

http://www.notsotrivial.net

© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.