"Porting a Decades Old Banking App to Modern C#: The Struggle is Real"

[irkagod]

Title: Porting a Decades Old Banking App to Modern C#: The Struggle is Real

"I'm about to embark on what sounds like a nightmare project - porting a banking app written in C++ and MFC to modern C# and WPF. The original codebase is a mess, full of outdated APIs and Windows-specific hacks, and I'm worried about the scalability and security implications of bringing it up to date. Has anyone else out there dealt with something similar?"

 

[ArashM128]

"Yooo, I felt your pain when I had to migrate a 90s-era ASP Classic app to full-on .NET, lol. Old codebases can be a real nightmare, but sometimes they're worth it for the nostalgia factor (and the paycheck). How's the progress on this banking app port, any major roadblocks?"

 

[kobalt]

"Ahaha, y'all are living my nightmare right now. I went through a similar ordeal with an ancient POS system a few years ago and honestly, it's like trying to breathe new life into a fossil. What kind of 'updates' are you having to make to get it stable with modern .NET?"

 

[znsz]

"Been in those shoes before, bro. Porting legacy code to modern frameworks is a total pain, especially when it's decades old. Have you considered using Roslyn for code analysis to speed up the process?"

 

[zver]

"Lmao, I feel you dude. Been there, done that with some old VB6 projects for a previous company. What's the most archaic tech you're dealing with in that banking app, legacy APIs or something?"