C1FlexGrid NutGet package and .NET Core 3.1 app

Posted by: wknauf on 2 May 2020, 10:00 pm EST

    • Post Options:
    • Link

    Posted 2 May 2020, 10:00 pm EST

    Just doing first steps with a .NETCore 3.1 application…

    After adding the C1FlexGrid NuGet package (version .416), I see these warnings:

    
    Warning	NU1701	Package 'C1.Win.C1Command 4.5.20201.416' 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' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project.
    Warning	NU1701	Package 'C1.Win.C1Input 4.5.20201.416' 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' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project.
    
    

    In my local directory “%USER_HOME%.nuget\packages\c1.win.c1flexgrid\4.5.20201.416\lib”, I find “C1.Win.C1FlexGrid.SearchPanel.4.5.2.dll” in subdir “net452”, but not in “netcoreapp”. Is this a packaging bug, or is SearchPanel not supported in .NET Core?

    It seems that the C1FlexGrid package also pulls in the “C1.Win.C1FlexGrid.GroupPanel.4.5.2” and “C1.Win.C1FlexGrid.SearchPanel.4.5.2” assemblies - I would expect them to be in separate packages to keep the C1FlexGrid assembly smaller: without those two additional assemblies, C1FlexGrid would not require “C1.Win.C1Input” and “C1.Win.C1Command” at all.

    Best regards

    Wolfgang

  • Posted 4 May 2020, 1:36 am EST

    Hi Wolfgang,

    I can observe the warnings. So, I have forwarded it to the developers for further investigation [Id: 434053]. Also, I have forwarded your concerns & suggestions to them. I will update you once we receive some information.

    Thanks,

    Ruchir

  • Posted 23 May 2020, 12:08 am EST

    Warning is fixed with build .424.

    Thanks a lot!

    Best regards

    Wolfgang

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels