从经典 ASP 到 .net 的迁移灾难
有谁有过从经典 Asp 迁移到 .Net 的公司表现不佳的经历吗？
在这家公司中，代表解决方案的“文件夹”图标和代表项目的“文件夹”图标以及代表文件目录的“文件夹”图标都是相同的东西。
.Net IDE 只是一个更好的记事本。
整个公司都在一个庞大的解决方案中。 应该有许多完全独立的项目的代码全部混合在“主解决方案”中的一组“文件夹”中并分布在其中。 每个文件夹都包含该地方在 .Net 中创建的所有应用程序的各种信息。
我的问题是这样的公司会怎样？ 他们会倒闭吗？ 他们是否会无限期地坚持下去，坚持同样的、劳动密集型的“代码库”维护噩梦，而真正的 .Net 程序员都无法忍受？ 他们能看到光明吗？ 如果是这样，怎么办？
我必须知道。
Does anyone have experience with companies that have migrated from classic Asp to .Net badly?
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.
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.
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?
I must know.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
有可能，他们不会迁移。 该代码仍然有效，只是太旧了。 最有可能发生的情况是，该项目将一次替换一小部分，但不会替换整体策略。 这将是缓慢而乏味的。 将会讨论重写应用程序，但它永远不会真正发生。 很多地方都有这样的心态，没坏就不修。 如果它能满足他们的需要，它就会存在很长一段时间。
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.
我在一家拥有 30,000 个内部网页面的公司工作。用经典的 asp 编写。 更不用说 200 多个 ASP 和 VB 组件的互联网应用程序。 ;-)
我们仍然在网上获得了良好的业务（几乎 60%）。 不能很快迁移。 我们慢慢地做。 更好地在.net 中进行新项目。 我同意凯文的观点，如果它有效，为什么要破坏它。
大多数时候，如果企业运作正常，企业并没有找到任何迁移的充分理由。
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. ;-)
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.
Mos of the time the business dont se any good reason to migrate if its working properly.
但它还有效吗？ 如果确实如此，那么为什么，特别是在当前的经济形势下，您会升级吗？ 只是为了好玩吗？ 需要有一个更好的理由。
每次 Glidden 推出一种新的/更好的、应该使用寿命更长的配方时，你是否会把房子上的所有油漆刮掉并重新粉刷？ 可能不会。 当需要重新粉刷时，您可以重新粉刷它。
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.
这篇优秀的文章很旧，但绝对总结了“新与旧”技术之争，以及它对商业的实际意义。
如果旧技术是一种经过验证的、稳定的赚钱工具，那么用更新的语言重写它只会增加风险。
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.