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.
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.