So, what is the solution for moving TrackableEntities.Client-based codebases to .Net Core?
I understand from the discussion in #7 that some of it should be re-architected, but what about a direct port/rebuild in the interim?
Specifically, I get these warnings with the TrackableEntities.Client 2.5.7 library in my .Net 9 client-side app...
warning NU1701: Package 'TrackableEntities.Client 2.5.7' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net9.0'. This package may not be fully compatible with your project.
So, what is the solution for moving TrackableEntities.Client-based codebases to .Net Core?
I understand from the discussion in #7 that some of it should be re-architected, but what about a direct port/rebuild in the interim?
Specifically, I get these warnings with the TrackableEntities.Client 2.5.7 library in my .Net 9 client-side app...
warning NU1701: Package 'TrackableEntities.Client 2.5.7' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net9.0'. This package may not be fully compatible with your project.