Not the same guy but I work for a company that has a similar code base. The project originally started 20 years ago as a C++ application. Parts have then been m

Not the same guy but I work for a company that has a similar code base. The project originally started 20 years ago as a C++ application. Parts have then been migrated to a C#/ASP.NET web app. But since migration never completed and the original C++ application is still in use, the web app ends up calling those C++ assemblies on the back end. Now, newer components are being started/migrated to .NET 5 and some of the C# code ends up being duplicated and we are basically maintaining C++, .NET Framework and .NET 5. Would not recommend.