Migration disaster from classic asp to .net
Does anyone have any experience with companies that have made a bad transition from classic Asp to .Net?
In this company, the folder icon, which represents the solution, and the folder icon, which represents the project, and the folder icon, which represents the file directory, are the same.
.Net IDE is the best notepad.
The whole company is in one massive solution. The code for what there should be many, completely separate projects, everything is mixed inside and distributed among a set of "folders" in the "Master Solution". Each of these folders contains variegated information for any application ever created in .Net.
My question is what is happening with these companies? Are they going out of business? They stay with him indefinitely, adhering to the same time-consuming "code base" supporting the nightmare that no real .Net programmer can stand? Do they ever see the light? If so, how?
I need to know.
They might not migrate. The code still works, it's just old. What will most likely happen is that the project is replaced by a small part at a time, but not by the overall strategy. It will be slow and hard. There will be talk of rewriting the application, but that will never happen. Many places have a mentality, if they are not broken, don't fix it. If he does what they need, it will last a long time.
a source to share
I work for a company that has an intranet of 30,000 pages. Written in classic asp. Not to mention 200+ web applications with ASP and VB components .; -)
We are still getting good business (almost 60%) on the internet. Can't migrate soon. We do it slowly. Better to do new projects in .net. I agree with Kevin if it works, why did he break it.
Mosh of the time when the business does not have any good reason to migrate if it is working properly.
a source to share
But does it still work? If so, why, especially in this economy, would you upgrade? just for this? There must be a better reason.
You peel off all the paint from your house and repaint it every time. Glidden introduces a new / better formula that should last longer? Probably no. You redraw it when it needs to be recolored.
a source to share
This excellent article is out of date, but certainly sums up the "new or old" technology debate and what it actually means for business.
If old technology is a proven, stable moneymaker, rewriting it in a newer language only increases the risk.
a source to share