Hmm, mixing old .NET Framework 4.8 stuff with .NET 8? I’ve heard people sometimes get it working by tweaking the app.config or using binding redirects to handle version conflicts, especially for missing assemblies like System.Net.Http.WebRequest. Maybe try the .NET Portability Analyzer tool to see which parts of the old libraries are incompatible—though I’m not sure if that’s still a thing. You could also experiment with manually adding assembly references or even copying DLLs directly into the output folder though that feels hacky. Some folks online mentioned creating a facade project that wraps the old libraries, maybe with some compatibility NuGet packages, but I’ve never tried it. Honestly, it might just be easier to bite the bullet and update chunks of the old code incrementally, targeting .NET Standard where possible. But yeah, no guarantees, some dependencies just won’t play nice with the newer framework.