Is a compiler warning about .NET core 7.0 expected for a newly created RhinoCommon plugin using the McNeel template?
TestOf70.zip (255.6 KB)
Visual Studio 2022 with the Rhino template extension v18.104.22.168 installed.
rhino_en-us_8.0.23264.09003 (sept 21 build)
Create a new RhinoCommon project. Pick V8 as the target.
Upon the solution getting created, there’s a warning on the 7.0 dependency warning for the RhinoCommon package.
This warning is repeated when compiling:
1>C:\devrepro\TestOf70\TestOf70\TestOf70.csproj : warning NU1701: Package ‘RhinoCommon 8.0.23164.14305-wip’ 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 ‘net7.0’. This package may not be fully compatible with your project.
The only thing I see in discourse is from back in V6, with this being an indication that (as then but not now expected), Rhino didn’t use Core:
How to use rhinocommon in dotnetcore project for IOS build - Rhino Developer - McNeel Forum
Is this a Rhino issue, do I have a broken install, or is it a result of Rhino supporting 4.8 and 7.0 which isn’t actually an issue to deploy (Win+Mac)?