Does anyone have experience with companies that have migrated from classic Asp to .Net badly?
有没有人有经验从那些从经典的Asp迁移到.Net的公司呢?
In this company, the "folder" icon that represents a Solution and the "folder" icon that represents a Project and the "folder" icon that represents a file directory are all the same thing.
在该公司中,表示解决方案的“文件夹”图标和表示项目的“文件夹”图标以及表示文件目录的“文件夹”图标都是相同的。
The .Net IDE is just a better notepad.
.Net IDE只是一个更好的记事本。
The entire company is in one massive Solution. The code for what should be many, completely separate Projects is all intermixed within and spread out amongst a set of "folders" in the "Master Solution". Each of these folders contains motley information for any and every application the place has ever created in .Net.
整个公司都在一个庞大的解决方案中。应该是多个完全独立的项目的代码在“主解决方案”中的一组“文件夹”中混合并分散。这些文件夹中的每一个都包含该地点曾在.Net中创建的任何应用程序的杂乱信息。
My question is what happens to companies like this? Do they go out of business? Do they stay with it indefinitely, sticking with the same, labor-intensive "code base" maintenance nightmare that no real .Net programmer can stand? Do they ever see the light? If so, how?
我的问题是这样的公司会发生什么?他们破产了吗?他们是否无限期地坚持下去,坚持使用同样的,劳动密集型的“代码库”维护噩梦,真正的.Net程序员无法忍受?他们有没有看到光明?如果是这样,怎么样?
I must know.
我必须知道。
4 个解决方案
#1
It's possible, they won't migrate. The code still works, it's just old. Most likely what would happen is that the project will be replaced a small part at a time, but not with an overall strategy. It will be slow and drudging. There will be talks about rewriting the application, but it will never actually happen. A lot of the places have the mentality, if it isn't broken don't fix it. If it does what they need it to do, it will be around for a long time.
有可能,他们不会迁移。代码仍然有效,它只是旧的。最有可能的是,项目将一次取代一小部分,而不是整体战略。这将是缓慢和苦差事。将会有关于重写应用程序的讨论,但它永远不会真正发生。很多地方都有心态,如果没有破坏就不要修理它。如果它做了他们需要它做的事情,它将会存在很长时间。
#2
I work for the company which has as intranet 30,000 pages.. Written in classic asp. Not to mention the 200+ internet application sin ASP and VB components. ;-)
我为公司工作,内联网有30,000页。用经典的asp写的。更不用说200多个互联网应用程序错误的ASP和VB组件。 ;-)
We still get good business (almost 60%) online. Cant migrate soon. We do it slowly. Better do new projects in .net. I agree to Kevin if it works why broke it.
我们仍然在网上获得了良好的业务(近60%)。不能很快迁移。我们慢慢来。最好在.net中做新项目。我同意凯文,如果它起作用,为什么打破它。
Mos of the time the business dont se any good reason to migrate if its working properly.
如果工作正常,企业没有任何理由去迁移。
#3
But does it still work? If it does, than why, especially in this economy would you upgrade? just for the heck of it? There needs to be a better reason that that.
但它仍然有效吗?如果确实如此,那么,尤其是在这个经济体中你会升级吗?只是为了它?需要有一个更好的理由。
Do you scrape all the paint off of your house and re-paint it everythime Glidden introduces a new/better formula that is supposed to last longer? Probably not. You repaint it when it needs repainting.
你是否从你的房子里刮下所有的油漆并每隔一段时间重新粉刷它Glidden会推出一种新的/更好的配方,它应该持续更久?可能不是。你需要重新粉刷时重绘它。
#4
This excellent article is old, but definitely sums up the "new vs. old" technology debate, and what it actually means to business.
这篇优秀的文章很老,但绝对总结了“新旧”技术辩论,以及它对企业的实际意义。
If the old technology is a proven, stable money-maker, rewriting it in a newer language only adds risk.
如果旧技术是经过验证的,稳定的赚钱机器,用较新的语言重写它只会增加风险。
#1
It's possible, they won't migrate. The code still works, it's just old. Most likely what would happen is that the project will be replaced a small part at a time, but not with an overall strategy. It will be slow and drudging. There will be talks about rewriting the application, but it will never actually happen. A lot of the places have the mentality, if it isn't broken don't fix it. If it does what they need it to do, it will be around for a long time.
有可能,他们不会迁移。代码仍然有效,它只是旧的。最有可能的是,项目将一次取代一小部分,而不是整体战略。这将是缓慢和苦差事。将会有关于重写应用程序的讨论,但它永远不会真正发生。很多地方都有心态,如果没有破坏就不要修理它。如果它做了他们需要它做的事情,它将会存在很长时间。
#2
I work for the company which has as intranet 30,000 pages.. Written in classic asp. Not to mention the 200+ internet application sin ASP and VB components. ;-)
我为公司工作,内联网有30,000页。用经典的asp写的。更不用说200多个互联网应用程序错误的ASP和VB组件。 ;-)
We still get good business (almost 60%) online. Cant migrate soon. We do it slowly. Better do new projects in .net. I agree to Kevin if it works why broke it.
我们仍然在网上获得了良好的业务(近60%)。不能很快迁移。我们慢慢来。最好在.net中做新项目。我同意凯文,如果它起作用,为什么打破它。
Mos of the time the business dont se any good reason to migrate if its working properly.
如果工作正常,企业没有任何理由去迁移。
#3
But does it still work? If it does, than why, especially in this economy would you upgrade? just for the heck of it? There needs to be a better reason that that.
但它仍然有效吗?如果确实如此,那么,尤其是在这个经济体中你会升级吗?只是为了它?需要有一个更好的理由。
Do you scrape all the paint off of your house and re-paint it everythime Glidden introduces a new/better formula that is supposed to last longer? Probably not. You repaint it when it needs repainting.
你是否从你的房子里刮下所有的油漆并每隔一段时间重新粉刷它Glidden会推出一种新的/更好的配方,它应该持续更久?可能不是。你需要重新粉刷时重绘它。
#4
This excellent article is old, but definitely sums up the "new vs. old" technology debate, and what it actually means to business.
这篇优秀的文章很老,但绝对总结了“新旧”技术辩论,以及它对企业的实际意义。
If the old technology is a proven, stable money-maker, rewriting it in a newer language only adds risk.
如果旧技术是经过验证的,稳定的赚钱机器,用较新的语言重写它只会增加风险。