Nuget packages for 4.5.2 components

Nuget packages for 4.5.2 components

Posted by: wknauf on 19 April 2022, 12:43 am EST

• 

  wknauf

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 19 April 2022, 12:43 am EST - Updated 3 October 2022, 1:31 pm EST

  Hi C1,

  two questions about the NuGet packages for the 4.5.2 edition:

  a) for some packages that are .NET6 compatible and the new versions have the same name, there are updates suggested for the .NET5 and .NET6 versions.
  
  So, there will always be update notifications, though I have to stay with the 4.5.2 versions.

  

  1211×814 47.5 KB

  I don’t know the details of NuGet, but I would expect that a package can declare that it does not support .NET framework?

  b) attached sample uses three packages.
  
  DockingTabTester.zip
  
  When trying to update “C1.Win.Ribbon” from .532 to .548, there is this error message:

  NU1107: Version conflict detected for C1.Win. Install/reference C1.Win 4.5.20221.548 directly to project DockingTabTester to resolve this issue. 
   DockingTabTester -> C1.Win.Ribbon 4.5.20221.548 -> C1.Win (>= 4.5.20221.548) 
   DockingTabTester -> C1.Win.C1Command 4.5.20213.532 -> C1.Win (= 4.5.20213.532).
  

  

  1257×754 50.2 KB

  It works if I add the “C1.Win” package explicitely. This should not be necessary, as it is probably part of C1.Win.Ribbon and C1.Win.C1Command.
  
  Any chance to improve this?

  Best regards

  Wolfgang

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 19 April 2022, 10:52 pm EST

  Hi Wolfgang,

  We have shared your concerns with the development team to get their insights on it. We will let you know as soon as we have an update.

  Kind Regards,
  
  Kartik

  [Internal Tracking ID: C1WIN-27253]

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 17 January 2023, 6:32 pm EST

  Any updates on this?

  About question a: it seems Nuget does not support filtering the suggested updates by supported target framework, see e.g. https://github.com/NuGet/Home/issues/5725

  Best regards

  Wolfgang

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 17 January 2023, 11:27 pm EST

  Hi Wolfgang,

  This issue is on the to-do list of the development team and they currently discussing this among the team. They have provided an ETA of 2023v2 release. We will let you know as soon as there is an update on the issue.

  Thanks, and Best Regards,
  
  Kartik

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 16 January 2024, 2:30 am EST

  Any updates on this? The 2023v2 release has arrived long ago, but I don’t know what was changed with respect to this question ;-).

  Best regards

  Wolfgang

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 16 January 2024, 2:11 pm EST

  Hi Wolfgang,

  Apologies for not notifying you earlier, but this behavior was fixed in the latest 2023v3 (631) release, with the introduction of the new “8.0” versioning as discussed in (https://developer.mescius.com/forums/winforms-edition/nuget-package-versions-8-0-20233-631).

  The new “8.0” versioning is a unified versioning, that is compatible with all the currently supported .NET Frameworks, which is why these NuGet packages update to their respective latest version (8.0.20233.631 currently) without showing any errors or a constant update notification. Please see the following screenshot for reference - Unified versioning.zip

  We have also attached a video showing the update behavior with the latest versioning - Avi_NugetUpdate.zip

  Thanks, and Best Regards,
  
  Kartik

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 16 January 2024, 6:02 pm EST

  Thanks! That is good to hear!

  Best regards

  Wolfgang