3 ms·
That's very insightful, and I just wish I had the ability to explain this to non-technical managers. "But it was working!" "Sure, 10 years ago, now I can't ev
by jiggawatts 2y ago
That's very insightful, and I just wish I had the ability to explain this to non-technical managers.
"But it was working!"
"Sure, 10 years ago, now I can't even find a version of Visual Studio that will install that can even open the project, let alone compile it."
- actionfromafar 2y agoAnd VS on an old laptop or Virtualbox might actually work, still. Good luck recreating some random services tangle from the year 2024 in 2034.
- jiggawatts 2y agoSince Visual Studio is Windows only, the straightforward solution that I used was to install an old version in a Hyper-V virtual machine. Then it's a multi-step process where the project is upgraded inside the VM with an ancient VS copy as "far as it'll go", then copied out to the external environment with VS 2022 that also has the 2016 and 2019 "Build Tools" installed. Then the projects can be upgraded to "current day". In some cases I just gave up and created new empty projects with identical names and GUIDs, then copy-pasted the code files across. It can be simpler and faster.