Re: ASP to ASP.NET
From: Kevin Spencer (kevin_at_DIESPAMMERSDIEtakempis.com)
Date: 02/22/05
- Next message: Brian: "inserting multiple records....."
- Previous message: glenn: "Re: asp question about post vars"
- In reply to: Kevin: "ASP to ASP.NET"
- Next in thread: Scott M.: "Re: ASP to ASP.NET"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 15:34:35 -0500
Time is money indeed. If you have the time, and you have the inclination,
why not? On the other hand, the old saying goes "if it ain't broke, don't
fix it." IOW, you might want to wait for the next version, or some point at
which you need to make a lot of changes, in order to minimize the expense.
As far as the end user goes, it doesn't make any difference.
-- HTH, Kevin Spencer Microsoft MVP .Net Developer Neither a follower nor a lender be. "Kevin" <kevin@DearingerAM.com> wrote in message news:eRVCxuRGFHA.208@TK2MSFTNGP12.phx.gbl... I have a fairly extensive and complicated ASP 3.0 app that is in use by about 10 clients and hundreds of users. Should I devote the time to migrate? Where can I see the pros and cons of a conversion? I've meddled a bit with .NET and recognize the obvious benefits, but... TIME IS MONEY. Any recommendations? Kevin
- Next message: Brian: "inserting multiple records....."
- Previous message: glenn: "Re: asp question about post vars"
- In reply to: Kevin: "ASP to ASP.NET"
- Next in thread: Scott M.: "Re: ASP to ASP.NET"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
