Channels ▼

Web Development

ASP to ASP.NET Migration Strategy

May, 2005: ASP to ASP.NET Migration Strategy

1. The investment in legacy code is preserved.
2. Relatively small risk associated with the migration process.
3. Relatively low cost of migration.
4. Personnel are in place, trained, and the application delivers a service today.
5. New functionality can be added separately, minimally affecting existing code.
6. New functionality added in .NET, gains .NET benefits.
1. Legacy code and .NET code have to coexist. This adds additional cost in maintaining two different environments. Both environments have to be deployed and supported.
2. Application and session states of ASP and ASP.NET live in different processes and have to be synchronized. This involves additional cost in development, testing, and support.
3. Legacy code does not gain productivity, maintainability, extensibility, performance, and other .NET benefits.
4. Performance of interoperability between legacy code and .NET can possibly be an issue.
5. Application architecture as a whole is not consistent. Legacy and .NET application parts have different architectures.
6. The common functionality for legacy and new .NET code has to be maintained. Possible solutions are discussed below.
7. Some legacy code changes are necessary to communicate with the .NET part of the application.
8. The problem of adding new functionality that affects legacy code can achieve significant magnitude, possibly resulting in migration or rewrite anyway.
9. The timeout problem should be resolved. ASP and ASP.NET application parts have separate timeout settings.

Table 1: Pros and cons of a side-by-side approach.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.