I did that.
Instead of improving the compiler is now producing more errors.
My code references ConsoleX.
I downloaded CosoleX from GitHub and included the source code in my project.
ConsoleUI.cs contains the statement "using System.Windows.Forms".
When I use .NET Framework 4.8 I include the reference "System.Windows.Form" and such an error disappears.
Now I am using .NET Core 6.0. I still include the reference (attached snapshot) "System.Windows.Form" but the error does not disappear.
In fact, in the Framework list of the Solution Explorer, I can see System.Windows but I cannot see System.Windows.Forms.
If NET Core 6.0 were not supporting the reference to such an assembly I would expect I could not find it as a possible reference to add. It should be filtered out. But it is not.
Furthermore, the compiler is now marking other errors in the source code ConsoleUI.cs
I have to point out that ConsoleX is a package that targets .NET Framework 4.8
I include its source code in my project that is targeting .NET 6.0
Is this sort of "mix & match" feasible or is it nonsense?
Thank you so much.