Log in to start a topic

Unable to load NuGets with AR14 in Visual Studio 2019

Posted by: jason.butera on 21 January 2020, 9:26 am EST

  • jason.butera

    • Post Options:
    • Link
      Copy

    Posted 21 January 2020, 9:26 am EST - Updated 30 September 2022, 7:22 am EST

    I created a .Net Standard 2.0 class library and attempted to add an Active Reports 14 Section Report (code-based) item. It starts installing the NuGet dependencies, but quickly fails and rolls back with the following message:

    As a result, I’m unable to view the designer or work at all with the report. Any help would be appreciated. I’m currently using VS2019 version 16.4.3 and AR 14.0.19026.0.

  • mohitg

    Posted 21 January 2020, 5:12 pm EST

    Hello Jason,

    There is some problem with the Codebase report with the release build. We are working on this and will provide you the hotfix in end of this week or the start of next week.

    Thanks,

    Mohit

  • mohitg

    Posted 23 January 2020, 5:18 pm EST

    Hello,

    Could you please check with the latest hotfix of the AR. You can download the same from the following link:

    https://cdn.grapecity.com/ActiveReports/AR14/ActiveReports-v14.0.19213.msi

    Note: You should manually add a reference to Serializer NuGet package after update

    Also, if the problem still occurs:

    Try to reset VS (https://docs.microsoft.com/en-us/visualstudio/ide/reference/resetsettings-devenv-exe?view=vs-2019)

    Thanks,

    Mohit

  • jason.butera

    Posted 24 January 2020, 5:08 am EST - Updated 30 September 2022, 7:22 am EST

    No luck. I get this error before and after using /ResetSettings

    If I try to install that package manually, I get the following errors:

    Detected package downgrade: System.Memory from 4.5.1 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.Rendering 1.5.3100 → System.Data.SqlClient 4.6.1 → System.Memory (>= 4.5.1)

    ClassLibrary1 → System.Memory (>= 4.5.0)

    Detected package downgrade: System.Memory from 4.5.1 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.Drawing.Gc 1.5.3100 → System.Data.SqlClient 4.6.1 → System.Memory (>= 4.5.1)

    ClassLibrary1 → System.Memory (>= 4.5.0)

    Detected package downgrade: System.Memory from 4.5.3 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.Drawing.Gdi 1.5.3100 → System.Configuration.ConfigurationManager 4.6.0 → System.Security.Cryptography.ProtectedData 4.6.0 → System.Memory (>= 4.5.3)

    ClassLibrary1 → System.Memory (>= 4.5.0)

    Detected package downgrade: System.Memory from 4.5.3 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.Rendering 1.5.3100 → System.Configuration.ConfigurationManager 4.6.0 → System.Security.Cryptography.ProtectedData 4.6.0 → System.Memory (>= 4.5.3)

    ClassLibrary1 → System.Memory (>= 4.5.0)

    Detected package downgrade: System.Memory from 4.5.3 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.DataProviders 1.5.3100 → System.Data.OleDb 4.6.0 → System.Memory (>= 4.5.3)

    ClassLibrary1 → System.Memory (>= 4.5.0)

    Detected package downgrade: System.Memory from 4.5.1 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.Drawing.Gdi 1.5.3100 → System.Data.SqlClient 4.6.1 → System.Memory (>= 4.5.1)

    ClassLibrary1 → System.Memory (>= 4.5.0)

    Detected package downgrade: System.Memory from 4.5.1 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.DataProviders 1.5.3100 → System.Data.SqlClient 4.6.1 → System.Memory (>= 4.5.1)

    ClassLibrary1 → System.Memory (>= 4.5.0)

    Detected package downgrade: System.Buffers from 4.5.0 to 4.4.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.DataProviders 1.5.3100 → System.Data.OleDb 4.6.0 → Microsoft.Win32.Registry 4.6.0 → System.Buffers (>= 4.5.0)

    ClassLibrary1 → System.Buffers (>= 4.4.0)

    Detected package downgrade: System.Memory from 4.5.3 to 4.5.0. Reference the package directly from the project to select a different version.

    ClassLibrary1 → GrapeCity.ActiveReports.Core.Drawing.Gc 1.5.3100 → System.Configuration.ConfigurationManager 4.6.0 → System.Security.Cryptography.ProtectedData 4.6.0 → System.Memory (>= 4.5.3)

    ClassLibrary1 → System.Memory (>= 4.5.0)

  • mohitg

    Posted 27 January 2020, 1:46 am EST

    Hello,

    Could you share the sample with us? Also, please make sure that your application FW set to 4.6.2 or higher as AR14 only supports the 4.6.2 or higher .Net FW.

    Thanks,

    Mohit

  • jason.butera

    Posted 27 January 2020, 5:18 am EST

    It’s a .Net Standard 2.0 Class library, not full framework.

  • mohitg

    Posted 27 January 2020, 10:24 pm EST

    Hello Jason,

    The .Net Standard 2.0 supports the 4.6.1 .Net FW. SO, When you try to add the AR packages, NuGet considers the FW of application is 4.6.1 that’s why this issue occurs. Please refer to the following page for more information:

    https://docs.microsoft.com/en-us/dotnet/standard/net-standard

    Could you please change the your application to .Net Standard 2.1

    Thanks,

    Mohit

  • snellcb

    Posted 28 February 2020, 9:47 am EST - Updated 30 September 2022, 7:22 am EST

    I’m experiencing similar issues trying to add a Section Report (code-based) to a C# class library (.net standard 2.1). ActiveReports v14.0.19213.0, Visual Studio 2019 16.4.5. Package installation fails

    I tried restoring one of the packages (GrapeCity.ActiveReports.Core.Rendering) manually and observed the following output and errors:

    Restoring packages for D:\Project\Eval\ActiveReports\ActiveReports.csproj…

    GET https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.rendering/index.json

    OK https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.rendering/index.json 128ms

    GET https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.rendering/1.5.3300/grapecity.activereports.core.rendering.1.5.3300.nupkg

    OK https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.rendering/1.5.3300/grapecity.activereports.core.rendering.1.5.3300.nupkg 103ms

    GET https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.dataproviders/index.json

    OK https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.dataproviders/index.json 122ms

    GET https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.dataproviders/1.5.3300/grapecity.activereports.core.dataproviders.1.5.3300.nupkg

    OK https://api.nuget.org/v3-flatcontainer/grapecity.activereports.core.dataproviders/1.5.3300/grapecity.activereports.core.dataproviders.1.5.3300.nupkg 105ms

    Installing GrapeCity.ActiveReports.Core.DataProviders 1.5.3300.

    Installing GrapeCity.ActiveReports.Core.Rendering 1.5.3300.

    NU1701: Package ‘GrapeCity.ActiveReports.Chart 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1701: Package ‘GrapeCity.ActiveReports.Design.Win 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1701: Package ‘GrapeCity.ActiveReports.Document 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1701: Package ‘GrapeCity.ActiveReports.Export.Image 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1701: Package ‘GrapeCity.ActiveReports.Export.Rdf 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1701: Package ‘GrapeCity.ActiveReports.Interop 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1701: Package ‘GrapeCity.ActiveReports.Serializer 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1701: Package ‘GrapeCity.ActiveReports.Viewer.Win 14.0.19213’ 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 ‘.NETStandard,Version=v2.1’. This package may not be fully compatible with your project.

    NU1605: Detected package downgrade: GrapeCity.ActiveReports.Core.Rdl from 1.5.3300 to 1.5.3100. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Rendering 1.5.3300 → GrapeCity.ActiveReports.Core.Rdl (>= 1.5.3300 && < 2.0.0)

    ActiveReports → GrapeCity.ActiveReports.Core.Rdl (>= 1.5.3100)

    NU1605: Detected package downgrade: System.Memory from 4.5.1 to 4.5.0. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Rendering 1.5.3300 → System.Data.SqlClient 4.6.1 → System.Memory (>= 4.5.1)

    ActiveReports → System.Memory (>= 4.5.0)

    NU1605: Detected package downgrade: System.Memory from 4.5.3 to 4.5.0. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Rendering 1.5.3300 → System.Configuration.ConfigurationManager 4.6.0 → System.Security.Cryptography.ProtectedData 4.6.0 → System.Memory (>= 4.5.3)

    ActiveReports → System.Memory (>= 4.5.0)

    NU1605: Detected package downgrade: System.Memory from 4.5.3 to 4.5.0. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Rendering 1.5.3300 → GrapeCity.ActiveReports.Core.DataProviders 1.5.3300 → System.Data.OleDb 4.6.0 → System.Memory (>= 4.5.3)

    ActiveReports → System.Memory (>= 4.5.0)

    NU1605: Detected package downgrade: System.Buffers from 4.5.0 to 4.4.0. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Rendering 1.5.3300 → GrapeCity.ActiveReports.Core.DataProviders 1.5.3300 → System.Data.OleDb 4.6.0 → Microsoft.Win32.Registry 4.6.0 → System.Buffers (>= 4.5.0)

    ActiveReports → System.Buffers (>= 4.4.0)

    Package restore failed. Rolling back package changes for ‘ActiveReports’.

    After manually updating the System.* nuget packages (that AR had installed as dependencies) to latest stable versions, I was able to restore the missing GrapeCity.ActiveReports.Core.* nuget packages except:

    • GrapeCity.ActiveReports.Core.Drawing.Gc
    • GrapeCity.ActiveReports.Core.Export.Image.Page

    Here’s the info from those package restore attempts:

    GrapeCity.ActiveReports.Core.Drawing.Gc:

    ActiveReports → GrapeCity.ActiveReports.Core.Drawing.Gc 1.5.3300 → GrapeCity.Documents.Common (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.Common (>= 2.2.0.319)

    NU1605: Detected package downgrade: GrapeCity.Documents.Common.Windows from 2.2.0.320 to 2.2.0.319. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Drawing.Gc 1.5.3300 → GrapeCity.Documents.Common.Windows (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.Common.Windows (>= 2.2.0.319)

    NU1605: Detected package downgrade: GrapeCity.Documents.DX.Windows from 2.2.0.320 to 2.2.0.319. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Drawing.Gc 1.5.3300 → GrapeCity.Documents.DX.Windows (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.DX.Windows (>= 2.2.0.319)

    NU1605: Detected package downgrade: GrapeCity.Documents.Imaging from 2.2.0.320 to 2.2.0.319. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Drawing.Gc 1.5.3300 → GrapeCity.Documents.Imaging (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.Imaging (>= 2.2.0.319)

    Package restore failed. Rolling back package changes for ‘ActiveReports’.

    GrapeCity.ActiveReports.Core.Export.Image.Page:

    ActiveReports → GrapeCity.ActiveReports.Core.Export.Image.Page 1.5.3300 → GrapeCity.Documents.Common (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.Common (>= 2.2.0.319)

    NU1605: Detected package downgrade: GrapeCity.Documents.Common.Windows from 2.2.0.320 to 2.2.0.319. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Export.Image.Page 1.5.3300 → GrapeCity.Documents.Common.Windows (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.Common.Windows (>= 2.2.0.319)

    NU1605: Detected package downgrade: GrapeCity.Documents.DX.Windows from 2.2.0.320 to 2.2.0.319. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Export.Image.Page 1.5.3300 → GrapeCity.Documents.DX.Windows (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.DX.Windows (>= 2.2.0.319)

    NU1605: Detected package downgrade: GrapeCity.Documents.Imaging from 2.2.0.320 to 2.2.0.319. Reference the package directly from the project to select a different version.

    ActiveReports → GrapeCity.ActiveReports.Core.Export.Image.Page 1.5.3300 → GrapeCity.Documents.Imaging (>= 2.2.0.320 && < 3.0.0)

    ActiveReports → GrapeCity.Documents.Imaging (>= 2.2.0.319)

    Package restore failed. Rolling back package changes for ‘ActiveReports’.

  • mohitg

    Posted 2 March 2020, 2:54 am EST

    Hello,

    Could please try with the latest hotfix. You can download the same from the following link:

    http://cdn.grapecity.com/ActiveReports/AR14/Hotfixes/ActiveReports-v14.0.19484.msi

    Also, please uninstall the previous and then install the above one.

    Thanks,

    Mohit

  • snellcb

    Posted 4 March 2020, 3:14 am EST - Updated 30 September 2022, 7:23 am EST

    No luck. Adding a new Section Report (code-based) to a C# class library (.net standard 2.1) still fails. Using ActiveReports v14.0.19484, Visual Studio 2019 16.4.5. Error details:

    Here’s how the dependencies look after attempting this:

    403×547 9.22 KB

  • mohitg

    Posted 4 March 2020, 11:07 pm EST

    Hello,

    I have escalated the issue to our development team(278633) and will inform you once I got any information from them.

    Thanks,

    Mohit

  • snellcb

    Posted 23 March 2020, 3:05 am EST

    Hi Mohit - any update on this issue?

  • mohitg

    Posted 24 March 2020, 7:52 pm EST

    Hello,

    Sorry for the delay!

    I have discussed with the development and found that currently, it is a limitation of AR. SectionReports is not supported in .Net Standard environment.

    Thanks,

    Mohit

  • peter.herschel

    Posted 29 July 2022, 4:43 am EST

    Are code based section reports not supported in NET6 Winform apps in visual studio 2022?

    When I try to add one I get Package Error that ‘GrapeCity.ActiveReports.Serializer.VS2022 16.1.3’ was restored using '.NETFramework,Version=v4.8 instead of the project target framework net6.0-…

    Package ‘Microsoft.VisualStudio.DpiAwareness 6.1.28916’ was restored using '.NETFramework,Version=v4.8 instead of the project target framework net6.0-…

    Thanks

    -Pete

  • akshay.rajput

    Posted 31 July 2022, 11:49 pm EST

    Hi Pete,

    >> Are code based section reports not supported in NET6 Winform apps in visual studio 2022?

    Code based Section Reports are supported in .Net 6. However, the Visual Studio Integrated Designer is not supported for Code Based Section Reports in .Net Core, .Net 5, .Net 6. You can ignore these warnings. If you want to design code based section reports in .Net 6 please refer to the following page of our documentation:

    https://www.grapecity.com/activereportsnet/docs/latest/online/designing-code-based-section-reports-in-net-core.html

    For more information on this issue please refer to the following forum page:

    https://www.grapecity.com/forums/activereports/section-reports-dotnet-6-a

    Regards,

    Akshay

Need extra support?

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

Learn More

Forum Channels

  • © 2023 MESCIUS inc. All Rights Reserved.  ·  1.800.858.2739

    All product and company names herein may be trademarks of their respective owners.