ASP and ASP.NET applications running side by side during a migration

[lonsharim]

Hi all,

We have been approached by a company that have large 2 tier ASP based
website using SQL Server as the backend. These systems have been in place
for well over a decade with a small inhouse team doing any maintainance
required.

They now want to move to ASP.NET 2.0 in phases. Starting by doing any new
development work in ASP.NET while still maintaining their old code in ASP
with a minimal migration of code if required. Given the size of their
migration it seems to be the most workable solution for the moment.

1. The ASP pages have a truck load of session objects and application
variables and we need to find an elegant way to make use of them in our ASPX
pages.

2. As it is a 2 tier system, they have their entire business logic
encapsulated in functions grouped together in different ASP pages. Whenever
a page requires a function, they include the ASP page containing the
function. We want to find a way to make calls to these functions from our
..NET pages. We are not considering duplicating the business logic on the dot
net side because of the volume and because there is little or no
documentation available on hand.

I would really appreciate any pointers in the right direction.

TIA
-MW

[Jon Paal [MSMD]]

I think you've answered your own question. You can't be expected to do good work with huge limitations.

You can suggest a way forward, doing the job correctly now. They can accept the recommendation or not.

But when the customer starts to dictate how to do the programming, there can only be problems and dissatisfaction , or worse, a bad
reference on your work.

The customer should not constrain you to do things in a less-than-correct way. If they don't have the money to do the job right, or
you can't meet their budget constraints and do the job right, then it will not be a win-win situation.

"lonsharim" <mu************ @trellisys.netw rote in message news:1B******** *************** ***********@mic rosoft.com...

Jon,

Thanks for your response.

I agree with you. The problem is my client doesnt have the kind of resources to convert the entire system. The size of the project
is extremly large and they dont want to invest in a full scale migration. Thats a huge limitation when we are entrusted to suggest
a way forward.

-MW


"Jon Paal [MSMD]" <Jon[ nospam ]Paal @ everywhere dot comwrote in message news:eH******** ******@TK2MSFTN GP04.phx.gbl...

>You are proposing to build a hybrid system. This is not going to be desireable for the long term. I believe it would be better
to convert all now, rather than having to live with a hybrid and then converting remainder later.


"lonsharim" <mu************ @trellisys.netw rote in message news:22******** *************** ***********@mic rosoft.com...

>>Hi all,

We have been approached by a company that have large 2 tier ASP based website using SQL Server as the backend. These systems
have been in place for well over a decade with a small inhouse team doing any maintainance required.

They now want to move to ASP.NET 2.0 in phases. Starting by doing any new development work in ASP.NET while still maintaining
their old code in ASP with a minimal migration of code if required. Given the size of their migration it seems to be the most
workable solution for the moment.

1. The ASP pages have a truck load of session objects and application variables and we need to find an elegant way to make use
of them in our ASPX pages.

2. As it is a 2 tier system, they have their entire business logic encapsulated in functions grouped together in different ASP
pages. Whenever a page requires a function, they include the ASP page containing the function. We want to find a way to make
calls to these functions from our .NET pages. We are not considering duplicating the business logic on the dot net side because
of the volume and because there is little or no documentation available on hand.

I would really appreciate any pointers in the right direction.

TIA
-MW