11 ms·
The problem isn’t migrating the code, that’s actually doable. The problem is that we are maintaining actively developed apps that we want to keep on the latest
by alkonaut 8y ago
The problem isn’t migrating the code, that’s actually doable. The problem is that we are maintaining actively developed apps that we want to keep on the latest and greatest runtime, expect yearly performance improvements and also have tons of third party proprietary .Net 4.x dependencies for. The people manking those (one example in my case: AutoDesk) may or may not port these libs to core/5 ever. And without them we are stuck on the old framework and now even the old C# version.
It would be great to see a binary conversion/transpiler tool that converted 4.X libs to 5, checking the API compatibility and maybe even shimming some known holes.